Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a2d18f3b13445f2ff321c1f60c15f27c2d64786a78721a6983092ab7ffa8d3

Tx prefix hash: 3d9941a062f9441298689ad08e6e4771943a03b54f12cf925b3236a582cf81a7
Tx public key: 9c2054e396e941c5a83a961553e395ed9053a0df5c40c82d7a5234693faf7402
Timestamp: 1721944109 Timestamp [UCT]: 2024-07-25 21:48:29 Age [y:d:h:m:s]: 01:103:12:48:20
Block: 1073671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332468 RingCT/type: yes/0
Extra: 019c2054e396e941c5a83a961553e395ed9053a0df5c40c82d7a5234693faf740202110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c17b412eb18590f16f4a801605d6799247f1bf11dfd0c6c53ba2ca7580b4189d 0.600000000000 1546176 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": 1073681, "vin": [ { "gen": { "height": 1073671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c17b412eb18590f16f4a801605d6799247f1bf11dfd0c6c53ba2ca7580b4189d" } } ], "extra": [ 1, 156, 32, 84, 227, 150, 233, 65, 197, 168, 58, 150, 21, 83, 227, 149, 237, 144, 83, 160, 223, 92, 64, 200, 45, 122, 82, 52, 105, 63, 175, 116, 2, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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