Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea15d07406f0f13094c671561f9978ca55985aafbf58387414912b836670d268

Tx prefix hash: cf4843d53a42d0841f971fa6a37f15329599bd9e920e9e70f3532fc049e80db1
Tx public key: 239a1297db9d74b1e8c68575448bb3c6867d2ddadfc9b8f61b1be01e0b5b66e1
Timestamp: 1729210615 Timestamp [UCT]: 2024-10-18 00:16:55 Age [y:d:h:m:s]: 00:167:20:51:54
Block: 1133915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119746 RingCT/type: yes/0
Extra: 01239a1297db9d74b1e8c68575448bb3c6867d2ddadfc9b8f61b1be01e0b5b66e1021100000006e001d62b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a616073d8ee0305026d7fe6bb9872b92c1f7690d8de444057d80b1c41a0da87 0.600000000000 1617136 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": 1133925, "vin": [ { "gen": { "height": 1133915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a616073d8ee0305026d7fe6bb9872b92c1f7690d8de444057d80b1c41a0da87" } } ], "extra": [ 1, 35, 154, 18, 151, 219, 157, 116, 177, 232, 198, 133, 117, 68, 139, 179, 198, 134, 125, 45, 218, 223, 201, 184, 246, 27, 27, 224, 30, 11, 91, 102, 225, 2, 17, 0, 0, 0, 6, 224, 1, 214, 43, 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