Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbad68b672e1438befcc006bc9fb04729a980b114b7147d3f0d5aaf85e7a1b12

Tx prefix hash: 7dbce3f6ae171734971d11f807b3ee808da5c21074c62d08e6f316093d563b83
Tx public key: e288ac582add7e73d54797277634bad9fc69b9f7bbb2b81d6f7b501aad0eda3d
Timestamp: 1708310932 Timestamp [UCT]: 2024-02-19 02:48:52 Age [y:d:h:m:s]: 01:291:20:51:28
Block: 960646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467380 RingCT/type: yes/0
Extra: 01e288ac582add7e73d54797277634bad9fc69b9f7bbb2b81d6f7b501aad0eda3d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74b1a9e4ea2c6a1328df1033465031e351aedbfaf8d30e05519ece8c75f79612 0.600000000000 1420233 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": 960656, "vin": [ { "gen": { "height": 960646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74b1a9e4ea2c6a1328df1033465031e351aedbfaf8d30e05519ece8c75f79612" } } ], "extra": [ 1, 226, 136, 172, 88, 42, 221, 126, 115, 213, 71, 151, 39, 118, 52, 186, 217, 252, 105, 185, 247, 187, 178, 184, 29, 111, 123, 80, 26, 173, 14, 218, 61, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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