Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aa254377a52161bf349c8233d0f27e502ea4df1372f8c773effb18be4b9eb6b

Tx prefix hash: 3d74d7edb90791930ab18d5ff9279de98b63748a2d9e7e73145d9477578fb3c5
Tx public key: 2d5680b0b0aa9ae17cbe6fa0c73ba19d82bcedf200c78d8924f26e698dbbb80d
Timestamp: 1736877062 Timestamp [UCT]: 2025-01-14 17:51:02 Age [y:d:h:m:s]: 00:154:23:19:24
Block: 1197329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110463 RingCT/type: yes/0
Extra: 012d5680b0b0aa9ae17cbe6fa0c73ba19d82bcedf200c78d8924f26e698dbbb80d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36b976fe0df39782ae234a2813723f5ef27c284608266975171b49672c0aed1c 0.600000000000 1683936 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": 1197339, "vin": [ { "gen": { "height": 1197329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36b976fe0df39782ae234a2813723f5ef27c284608266975171b49672c0aed1c" } } ], "extra": [ 1, 45, 86, 128, 176, 176, 170, 154, 225, 124, 190, 111, 160, 199, 59, 161, 157, 130, 188, 237, 242, 0, 199, 141, 137, 36, 242, 110, 105, 141, 187, 184, 13, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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