Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e73b37a9b6684b8106b71b4411b91221b46a1cee2523a129b584fe031a8431f

Tx prefix hash: df679252f65eb0d6e837e219e3b870139b243f68757a2720b01302b5c4238172
Tx public key: 523c2b0b86347caa7c89ffa2e3b0c8b6004776c0b4a76679825382f882b83f0e
Timestamp: 1695507970 Timestamp [UCT]: 2023-09-23 22:26:10 Age [y:d:h:m:s]: 01:123:13:01:29
Block: 854701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349548 RingCT/type: yes/0
Extra: 01523c2b0b86347caa7c89ffa2e3b0c8b6004776c0b4a76679825382f882b83f0e021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.903692824000 dcy

stealth address amount amount idx
00: ffe5a1c56fcfea418722822a8518778eabad9a4c7739a130313dd81ee6e324a8 0.903692824000 1308687 of 0

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": 854711, "vin": [ { "gen": { "height": 854701 } } ], "vout": [ { "amount": 903692824, "target": { "key": "ffe5a1c56fcfea418722822a8518778eabad9a4c7739a130313dd81ee6e324a8" } } ], "extra": [ 1, 82, 60, 43, 11, 134, 52, 124, 170, 124, 137, 255, 162, 227, 176, 200, 182, 0, 71, 118, 192, 180, 167, 102, 121, 130, 83, 130, 248, 130, 184, 63, 14, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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