Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90d63b0e098dc37506d8e5d9cd7b8c1865899341a36d3a484c5cc2f02b11de7c

Tx prefix hash: e7d700fe26cc869737d562a48d6d2b92144c242250df54d07a49caa2096601a1
Tx public key: 7b39a4d7fc091bba5885c243f1f2f887687ee79c5bba6054ad4ccaaa60a1dbeb
Timestamp: 1729688031 Timestamp [UCT]: 2024-10-23 12:53:51 Age [y:d:h:m:s]: 00:031:18:32:17
Block: 1137842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22695 RingCT/type: yes/0
Extra: 017b39a4d7fc091bba5885c243f1f2f887687ee79c5bba6054ad4ccaaa60a1dbeb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c33de3e6d416667f13e7fc5eef0bc56788b864eb8f217b290521bfc5ff153fe 0.600000000000 1621411 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": 1137852, "vin": [ { "gen": { "height": 1137842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c33de3e6d416667f13e7fc5eef0bc56788b864eb8f217b290521bfc5ff153fe" } } ], "extra": [ 1, 123, 57, 164, 215, 252, 9, 27, 186, 88, 133, 194, 67, 241, 242, 248, 135, 104, 126, 231, 156, 91, 186, 96, 84, 173, 76, 202, 170, 96, 161, 219, 235, 2, 17, 0, 0, 0, 3, 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