Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73d287c85820f21831ae7cd7328ff7b2597879c7a51962b48542d651dceac694

Tx prefix hash: 61e34d290f0ea2f3d16d211b456b949568d2e5b89a17cf5edce98f1832fdcf62
Tx public key: 248d7118b83bc9a0e0ac4eca578343f7d95dcfe4f69440fa35d2ced822e8e9d7
Timestamp: 1694855236 Timestamp [UCT]: 2023-09-16 09:07:16 Age [y:d:h:m:s]: 01:200:12:02:11
Block: 849280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404382 RingCT/type: yes/0
Extra: 01248d7118b83bc9a0e0ac4eca578343f7d95dcfe4f69440fa35d2ced822e8e9d702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.941852435000 dcy

stealth address amount amount idx
00: 1e6e028937d2776a4c8838faa4c8358c3eef4bf3fdbf8d865bddc5dc1b5a36d8 0.941852435000 1302936 of 0

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": 849290, "vin": [ { "gen": { "height": 849280 } } ], "vout": [ { "amount": 941852435, "target": { "key": "1e6e028937d2776a4c8838faa4c8358c3eef4bf3fdbf8d865bddc5dc1b5a36d8" } } ], "extra": [ 1, 36, 141, 113, 24, 184, 59, 201, 160, 224, 172, 78, 202, 87, 131, 67, 247, 217, 93, 207, 228, 246, 148, 64, 250, 53, 210, 206, 216, 34, 232, 233, 215, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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