Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3998aaaa0fb9f5909ee837d67c987832e4afca9d03a0eac192807fe7523ce9c1

Tx prefix hash: c495f8416160a03c85a8ae624c8523fba50ca8af04d5dce948ecee471ae0273b
Tx public key: 7a4375942b610e602fc4321714bd4f74af0c10cfa48443d0e9a3e112d49486fe
Timestamp: 1732869203 Timestamp [UCT]: 2024-11-29 08:33:23 Age [y:d:h:m:s]: 00:115:15:37:49
Block: 1164152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82451 RingCT/type: yes/0
Extra: 017a4375942b610e602fc4321714bd4f74af0c10cfa48443d0e9a3e112d49486fe021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9c13771b8bd0875b151fe5d14d227ce481c9e02f00f946c404c20a28ea29c3 0.600000000000 1649825 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": 1164162, "vin": [ { "gen": { "height": 1164152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9c13771b8bd0875b151fe5d14d227ce481c9e02f00f946c404c20a28ea29c3" } } ], "extra": [ 1, 122, 67, 117, 148, 43, 97, 14, 96, 47, 196, 50, 23, 20, 189, 79, 116, 175, 12, 16, 207, 164, 132, 67, 208, 233, 163, 225, 18, 212, 148, 134, 254, 2, 17, 0, 0, 0, 4, 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