Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 801ae864d19bbfe3373e638bf21de09a141cbcbc86f3d98365ebbcc5c3c6445a

Tx prefix hash: 2a263d7dd79b84b4814c2808e5b2f8a55ba468208955d095177d89fc47d7f24a
Tx public key: 9c348afb63a59c8c5b24df8917a81bbdd3cbec7e95218f9292db1a647a45d740
Timestamp: 1587536213 Timestamp [UCT]: 2020-04-22 06:16:53 Age [y:d:h:m:s]: 04:227:03:15:40
Block: 94937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1072816 RingCT/type: yes/0
Extra: 019c348afb63a59c8c5b24df8917a81bbdd3cbec7e95218f9292db1a647a45d74002110000000f4ac5aa02000000000000000000

1 output(s) for total of 297.464454441000 dcy

stealth address amount amount idx
00: b35ada372ccbd7133474bf194e8ba4e088705209e182f2c3944f8913c94cae53 297.464454441000 168817 of 0

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": 94947, "vin": [ { "gen": { "height": 94937 } } ], "vout": [ { "amount": 297464454441, "target": { "key": "b35ada372ccbd7133474bf194e8ba4e088705209e182f2c3944f8913c94cae53" } } ], "extra": [ 1, 156, 52, 138, 251, 99, 165, 156, 140, 91, 36, 223, 137, 23, 168, 27, 189, 211, 203, 236, 126, 149, 33, 143, 146, 146, 219, 26, 100, 122, 69, 215, 64, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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