Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2668bd689d12fed3a5263d2a0e0e6f695e9c8da96cd0d27e0c06fd3502ea04b4

Tx prefix hash: 47df9b8b70c8be56d060edc60b3ffe407d9102c26c9efd8b63069f6ae228de27
Tx public key: cbe3efcf02d651cb0ec980eff163b8beec5e70bab8b499490d09d933164e211d
Timestamp: 1735317710 Timestamp [UCT]: 2024-12-27 16:41:50 Age [y:d:h:m:s]: 00:358:12:24:15
Block: 1184410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253812 RingCT/type: yes/0
Extra: 01cbe3efcf02d651cb0ec980eff163b8beec5e70bab8b499490d09d933164e211d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1bcce49641f48227a68a92ef410dca3491b402ca8f85811cbbd1a13e3165c56 0.600000000000 1670867 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": 1184420, "vin": [ { "gen": { "height": 1184410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1bcce49641f48227a68a92ef410dca3491b402ca8f85811cbbd1a13e3165c56" } } ], "extra": [ 1, 203, 227, 239, 207, 2, 214, 81, 203, 14, 201, 128, 239, 241, 99, 184, 190, 236, 94, 112, 186, 184, 180, 153, 73, 13, 9, 217, 51, 22, 78, 33, 29, 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