Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 027e8011514d8cdb5a9a7d3f77061c72379c77e84247253d4bea49ad0165abaf

Tx prefix hash: cd4d053ccfa939217272fac36dcb61d74bd7b6a2a29c5cd23c49613341fda531
Tx public key: f2504ce26c2eec4b8c90b241a6021d51d80ccc00f8603196477e7938b420c1a8
Timestamp: 1660684564 Timestamp [UCT]: 2022-08-16 21:16:04 Age [y:d:h:m:s]: 03:076:15:20:47
Block: 567359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 834574 RingCT/type: yes/0
Extra: 01f2504ce26c2eec4b8c90b241a6021d51d80ccc00f8603196477e7938b420c1a802110000000833af99f4000000000000000000

1 output(s) for total of 8.092900817000 dcy

stealth address amount amount idx
00: 6f7148ef5e3d61e21abbd9f64a339a9d9f468ca29261bcaa6bba55f1e120d29c 8.092900817000 1000460 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": 567369, "vin": [ { "gen": { "height": 567359 } } ], "vout": [ { "amount": 8092900817, "target": { "key": "6f7148ef5e3d61e21abbd9f64a339a9d9f468ca29261bcaa6bba55f1e120d29c" } } ], "extra": [ 1, 242, 80, 76, 226, 108, 46, 236, 75, 140, 144, 178, 65, 166, 2, 29, 81, 216, 12, 204, 0, 248, 96, 49, 150, 71, 126, 121, 56, 180, 32, 193, 168, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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