Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72cc4783c5424da989af9456e909fa8e676686ca16f1bfc8b2c841bd90d4a33

Tx prefix hash: 1959ac94a8c1c3edc30a2342bbcc1830ac61faad21f3064d641dfab1c545548d
Tx public key: fccc3799f9e77861c9c0f2703ad3cc07f4d9a71f3f3c732b33cba80fee30ef1e
Timestamp: 1716695540 Timestamp [UCT]: 2024-05-26 03:52:20 Age [y:d:h:m:s]: 00:297:06:52:07
Block: 1030167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212483 RingCT/type: yes/0
Extra: 01fccc3799f9e77861c9c0f2703ad3cc07f4d9a71f3f3c732b33cba80fee30ef1e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baac9c1cb29e505f8b3b24dcb4e9d9a46370200e01709a13582f5f4e2f5dbf9c 0.600000000000 1498420 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": 1030177, "vin": [ { "gen": { "height": 1030167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baac9c1cb29e505f8b3b24dcb4e9d9a46370200e01709a13582f5f4e2f5dbf9c" } } ], "extra": [ 1, 252, 204, 55, 153, 249, 231, 120, 97, 201, 192, 242, 112, 58, 211, 204, 7, 244, 217, 167, 31, 63, 60, 115, 43, 51, 203, 168, 15, 238, 48, 239, 30, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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