Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c939a9c21cd65e434fa2d95b398fb346da77fa8ef5abd95256024ef7e5b0432

Tx prefix hash: 692d45d5bfc905713682d8d32cc38e594ee836fa09e94e9ddf72cf9dcaa51845
Tx public key: 3dca1b9663d26def8bff191d0e7645e27fd121ca4f664cf86eb3443b9a9b97c6
Timestamp: 1704142023 Timestamp [UCT]: 2024-01-01 20:47:03 Age [y:d:h:m:s]: 01:096:13:59:12
Block: 926072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330135 RingCT/type: yes/0
Extra: 013dca1b9663d26def8bff191d0e7645e27fd121ca4f664cf86eb3443b9a9b97c6021100000004ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 284fe54d2ed610900bb1dd5dc78f3e5d9ad7563aad421767ad20c48e0cbe5178 0.600000000000 1383846 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": 926082, "vin": [ { "gen": { "height": 926072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "284fe54d2ed610900bb1dd5dc78f3e5d9ad7563aad421767ad20c48e0cbe5178" } } ], "extra": [ 1, 61, 202, 27, 150, 99, 210, 109, 239, 139, 255, 25, 29, 14, 118, 69, 226, 127, 209, 33, 202, 79, 102, 76, 248, 110, 179, 68, 59, 154, 155, 151, 198, 2, 17, 0, 0, 0, 4, 172, 50, 141, 17, 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