Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e867541928d952c479956a37fbfd9137f4ce4a7e0ec78c2be72081d212b210e1

Tx prefix hash: 1c0c213f444b8dbb88cf10a30c3afc434ce1f09a6b1cf3ff29860670387d153a
Tx public key: 14f03f276e9972320eba9e1e7e54730da788e4b6a3f1bd917761bca932849be2
Timestamp: 1702585037 Timestamp [UCT]: 2023-12-14 20:17:17 Age [y:d:h:m:s]: 02:024:19:47:03
Block: 913166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537556 RingCT/type: yes/0
Extra: 0114f03f276e9972320eba9e1e7e54730da788e4b6a3f1bd917761bca932849be202110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a18c821dcf5b82171c2905b2efd738b323b72eef375f59fe9482d28f68cdc07 0.600000000000 1370412 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": 913176, "vin": [ { "gen": { "height": 913166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a18c821dcf5b82171c2905b2efd738b323b72eef375f59fe9482d28f68cdc07" } } ], "extra": [ 1, 20, 240, 63, 39, 110, 153, 114, 50, 14, 186, 158, 30, 126, 84, 115, 13, 167, 136, 228, 182, 163, 241, 189, 145, 119, 97, 188, 169, 50, 132, 155, 226, 2, 17, 0, 0, 0, 5, 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