Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86a3078e4de07d9e9aa78ed9e02875c31f3a275b4e45d76b352ff7750cd9a2d3

Tx prefix hash: d3abb3cf9075c1b5f1caee51a02c6ce6e6475edecb5ae46a9648cc72c4b57932
Tx public key: 687a59f9c6207a46366ed3032e96027ef2808ac207218e8d91cb7395fc20169b
Timestamp: 1737079497 Timestamp [UCT]: 2025-01-17 02:04:57 Age [y:d:h:m:s]: 00:334:18:21:44
Block: 1199003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236799 RingCT/type: yes/0
Extra: 01687a59f9c6207a46366ed3032e96027ef2808ac207218e8d91cb7395fc20169b02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0354b4621ca9a93b3a5d05def146d628614fdcbcceaf089862f0c77b0aa6fd8 0.600000000000 1685630 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": 1199013, "vin": [ { "gen": { "height": 1199003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0354b4621ca9a93b3a5d05def146d628614fdcbcceaf089862f0c77b0aa6fd8" } } ], "extra": [ 1, 104, 122, 89, 249, 198, 32, 122, 70, 54, 110, 211, 3, 46, 150, 2, 126, 242, 128, 138, 194, 7, 33, 142, 141, 145, 203, 115, 149, 252, 32, 22, 155, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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