Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8f03b78dbcb7e9fd2e1177fd07d22efce075e5c02e6cb489afd7dde46ca57d8

Tx prefix hash: ef14c96053e86f94f256d68eba1bb0e177196201f34706dcaa2c522cfb109634
Tx public key: b0cae32254daea296e8a46a7f64156c0eae21d7a6caaf433776c040ab80f3251
Timestamp: 1705094845 Timestamp [UCT]: 2024-01-12 21:27:25 Age [y:d:h:m:s]: 01:304:20:41:14
Block: 933965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476718 RingCT/type: yes/0
Extra: 01b0cae32254daea296e8a46a7f64156c0eae21d7a6caaf433776c040ab80f32510211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50175d1e9abff9f13b470f7a389215739f1b51ef84cc18b8fa4b6bef65a38893 0.600000000000 1391949 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": 933975, "vin": [ { "gen": { "height": 933965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50175d1e9abff9f13b470f7a389215739f1b51ef84cc18b8fa4b6bef65a38893" } } ], "extra": [ 1, 176, 202, 227, 34, 84, 218, 234, 41, 110, 138, 70, 167, 246, 65, 86, 192, 234, 226, 29, 122, 108, 170, 244, 51, 119, 108, 4, 10, 184, 15, 50, 81, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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