Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec7c5648ee9de41a905db5b3c5614822558963147c04ff7d42576e919b247440

Tx prefix hash: a0d679ca84ef70320cf6c5e571b8fd899c221e94f0c25ba0a0e9c270055f28a3
Tx public key: 7a89fc46f2ebce024d5712ece7a7bb482666720de8b2b1e406ac6ad7d9f80d67
Timestamp: 1708986470 Timestamp [UCT]: 2024-02-26 22:27:50 Age [y:d:h:m:s]: 01:102:08:40:46
Block: 966257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334210 RingCT/type: yes/0
Extra: 017a89fc46f2ebce024d5712ece7a7bb482666720de8b2b1e406ac6ad7d9f80d670211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 859cd6e38bf11e08c52079e227de2c1d78e2b46ad7802d6224fbadf62d0abf0d 0.600000000000 1426014 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": 966267, "vin": [ { "gen": { "height": 966257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "859cd6e38bf11e08c52079e227de2c1d78e2b46ad7802d6224fbadf62d0abf0d" } } ], "extra": [ 1, 122, 137, 252, 70, 242, 235, 206, 2, 77, 87, 18, 236, 231, 167, 187, 72, 38, 102, 114, 13, 232, 178, 177, 228, 6, 172, 106, 215, 217, 248, 13, 103, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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