Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 032e65a0b10e8d87ed5e97b952e5532d2cd8eb65418c9f979155efffbf8ffcc3

Tx prefix hash: b6d0a298c9acbd629791c576c97dd6ce06330fa62c1aa8354dc473e998562b58
Tx public key: dffdb8f0730eb1ef7ebdd4873b0a7f58a68c26610027d26d8a62afedc62e05af
Timestamp: 1730646911 Timestamp [UCT]: 2024-11-03 15:15:11 Age [y:d:h:m:s]: 00:156:13:57:56
Block: 1145743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111736 RingCT/type: yes/0
Extra: 01dffdb8f0730eb1ef7ebdd4873b0a7f58a68c26610027d26d8a62afedc62e05af021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c2bd1c55acac73744f792958696fa5c45d939ecef01b94402e8f5432c5f859 0.600000000000 1630238 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1145753, "vin": [ { "gen": { "height": 1145743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c2bd1c55acac73744f792958696fa5c45d939ecef01b94402e8f5432c5f859" } } ], "extra": [ 1, 223, 253, 184, 240, 115, 14, 177, 239, 126, 189, 212, 135, 59, 10, 127, 88, 166, 140, 38, 97, 0, 39, 210, 109, 138, 98, 175, 237, 198, 46, 5, 175, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8