Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f62aaf3db59ff72ed7f9af025892acc9f65dc84f33759d5410616ceab648ac6

Tx prefix hash: f611452fe3e39957cfd8364f84ceeac1ae2c94b2ff99e6c6ea5af8712d10d516
Tx public key: 6f3a251751a1c411d145f370df2fc89774a92090c6d3750d8977a933425bb4cf
Timestamp: 1724323586 Timestamp [UCT]: 2024-08-22 10:46:26 Age [y:d:h:m:s]: 00:122:00:56:23
Block: 1093415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87310 RingCT/type: yes/0
Extra: 016f3a251751a1c411d145f370df2fc89774a92090c6d3750d8977a933425bb4cf02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6d95e4b43490069664ea5350c8d02f0a948fd4fb06064deeda8974cfec8a923 0.600000000000 1568354 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": 1093425, "vin": [ { "gen": { "height": 1093415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6d95e4b43490069664ea5350c8d02f0a948fd4fb06064deeda8974cfec8a923" } } ], "extra": [ 1, 111, 58, 37, 23, 81, 161, 196, 17, 209, 69, 243, 112, 223, 47, 200, 151, 116, 169, 32, 144, 198, 211, 117, 13, 137, 119, 169, 51, 66, 91, 180, 207, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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