Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7281f5c2f67fb2471fa761700c5809a94f869357b61db4ed0ba6b156e324f583

Tx prefix hash: d2c2900d058c64ce31c4a92006626ce842bbd6ae0f802d97dbe0691642ebd78a
Tx public key: 376d50f2cd443dd6c5c895d79158d5fd24bac23ff1a455d9d18df26fdc138aa5
Timestamp: 1730013157 Timestamp [UCT]: 2024-10-27 07:12:37 Age [y:d:h:m:s]: 00:143:16:23:23
Block: 1140535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102502 RingCT/type: yes/0
Extra: 01376d50f2cd443dd6c5c895d79158d5fd24bac23ff1a455d9d18df26fdc138aa5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4802a4bcda72ca5eb2cdb01468634633b09fddd87aede6103aceb6420c4d192 0.600000000000 1624336 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": 1140545, "vin": [ { "gen": { "height": 1140535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4802a4bcda72ca5eb2cdb01468634633b09fddd87aede6103aceb6420c4d192" } } ], "extra": [ 1, 55, 109, 80, 242, 205, 68, 61, 214, 197, 200, 149, 215, 145, 88, 213, 253, 36, 186, 194, 63, 241, 164, 85, 217, 209, 141, 242, 111, 220, 19, 138, 165, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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