Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5108c8c20fcebc48e24420ec538977a73a1fa88a081024385f8138ed027c1a45

Tx prefix hash: 5fb2ab508557a8e189a0df3d270140b0571d28ff422bae5272dcb11e0481a21f
Tx public key: 421fd9c95d58bd72f7815eecb18b5038b7c56c22a7b34743de7e14dcb32b45c4
Timestamp: 1735723701 Timestamp [UCT]: 2025-01-01 09:28:21 Age [y:d:h:m:s]: 00:106:11:13:15
Block: 1187777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75878 RingCT/type: yes/0
Extra: 01421fd9c95d58bd72f7815eecb18b5038b7c56c22a7b34743de7e14dcb32b45c4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17c1e6579968fce6617e7fa2185ac6cb49dcc7458cf66a0009848392c2d4a96e 0.600000000000 1674274 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": 1187787, "vin": [ { "gen": { "height": 1187777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17c1e6579968fce6617e7fa2185ac6cb49dcc7458cf66a0009848392c2d4a96e" } } ], "extra": [ 1, 66, 31, 217, 201, 93, 88, 189, 114, 247, 129, 94, 236, 177, 139, 80, 56, 183, 197, 108, 34, 167, 179, 71, 67, 222, 126, 20, 220, 179, 43, 69, 196, 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