Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a97123642682ccfc1c2eccd3e5c1eda0824995d7f87049b811374b189723c8d

Tx prefix hash: 16c86a78d1d067218abbd2d254ce1dfa31e87e7cbafd27209769ca3aa777342f
Tx public key: 617a1aad9e7c1f7cd8a6229cde21d8ed5445a7eedc83690ad2d232314cca30e3
Timestamp: 1706740596 Timestamp [UCT]: 2024-01-31 22:36:36 Age [y:d:h:m:s]: 01:063:03:00:25
Block: 947609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306184 RingCT/type: yes/0
Extra: 01617a1aad9e7c1f7cd8a6229cde21d8ed5445a7eedc83690ad2d232314cca30e302110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f36cbaae6265ba55854edf2e1a9b26c7bd55aa204c24a6e98699c6396616173a 0.600000000000 1405967 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": 947619, "vin": [ { "gen": { "height": 947609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f36cbaae6265ba55854edf2e1a9b26c7bd55aa204c24a6e98699c6396616173a" } } ], "extra": [ 1, 97, 122, 26, 173, 158, 124, 31, 124, 216, 166, 34, 156, 222, 33, 216, 237, 84, 69, 167, 238, 220, 131, 105, 10, 210, 210, 50, 49, 76, 202, 48, 227, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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