Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d95c707aabbcfe8cf0d9456536933fbfb9dcc53308878b762a88a1cd472104

Tx prefix hash: 5c3a47a4eb0f69ecb09a0e73af001351df2d51c89deeea0119d5fe663cd38eac
Tx public key: 755ac9126198b137d9a7de85f3fd0ecf4d4f46efa8f2018a596db2a78ffd62e1
Timestamp: 1743777204 Timestamp [UCT]: 2025-04-04 14:33:24 Age [y:d:h:m:s]: 00:219:13:38:49
Block: 1254189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154647 RingCT/type: yes/0
Extra: 01755ac9126198b137d9a7de85f3fd0ecf4d4f46efa8f2018a596db2a78ffd62e102110000000ba2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83d5c85e76e985fbf7259067f91f7bea365a977b824f603f93b959f6b3b49089 0.600000000000 1741270 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": 1254199, "vin": [ { "gen": { "height": 1254189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83d5c85e76e985fbf7259067f91f7bea365a977b824f603f93b959f6b3b49089" } } ], "extra": [ 1, 117, 90, 201, 18, 97, 152, 177, 55, 217, 167, 222, 133, 243, 253, 14, 207, 77, 79, 70, 239, 168, 242, 1, 138, 89, 109, 178, 167, 143, 253, 98, 225, 2, 17, 0, 0, 0, 11, 162, 237, 1, 107, 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