Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c49e9e61a5150e34d3b30e4112cdaef3c597440f0ca04f9676bdf6b9ebfaf70

Tx prefix hash: ec35868364343326df1ab22fe8900d1e9502b50c1497b56532992f13063cab1a
Tx public key: 9017a6f3c418aede83ab9bdf629c379fbd5a3059318454f7d7c352ca97e36f3a
Timestamp: 1708822427 Timestamp [UCT]: 2024-02-25 00:53:47 Age [y:d:h:m:s]: 01:037:16:02:41
Block: 964892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287929 RingCT/type: yes/0
Extra: 019017a6f3c418aede83ab9bdf629c379fbd5a3059318454f7d7c352ca97e36f3a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1064aeea69277c67f46db01ed3986dc75cce0ec1e7682d98e1bbf754fdf9820e 0.600000000000 1424635 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": 964902, "vin": [ { "gen": { "height": 964892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1064aeea69277c67f46db01ed3986dc75cce0ec1e7682d98e1bbf754fdf9820e" } } ], "extra": [ 1, 144, 23, 166, 243, 196, 24, 174, 222, 131, 171, 155, 223, 98, 156, 55, 159, 189, 90, 48, 89, 49, 132, 84, 247, 215, 195, 82, 202, 151, 227, 111, 58, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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