Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ebcdda5b313218292db13c3b58c2e3e3232d6934198a3683ec5bb9d0e3138b5

Tx prefix hash: 9ac08861208493e7d19ce4ee898f048c2e42a355e837b28b3fd9153fdb4fb3df
Tx public key: a8d5e5738d7fd87828110c7d44122d50296f7f8e76923e7fad6301cad1f85580
Timestamp: 1637946886 Timestamp [UCT]: 2021-11-26 17:14:46 Age [y:d:h:m:s]: 03:003:01:03:24
Block: 382680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 781047 RingCT/type: yes/0
Extra: 01a8d5e5738d7fd87828110c7d44122d50296f7f8e76923e7fad6301cad1f8558002110000000937cb3088000000000000000000

1 output(s) for total of 33.115421354000 dcy

stealth address amount amount idx
00: db3cfcf36a2bffed2fb26142710ba6061eae7a196099da23c0434ebe088ef26d 33.115421354000 772779 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": 382690, "vin": [ { "gen": { "height": 382680 } } ], "vout": [ { "amount": 33115421354, "target": { "key": "db3cfcf36a2bffed2fb26142710ba6061eae7a196099da23c0434ebe088ef26d" } } ], "extra": [ 1, 168, 213, 229, 115, 141, 127, 216, 120, 40, 17, 12, 125, 68, 18, 45, 80, 41, 111, 127, 142, 118, 146, 62, 127, 173, 99, 1, 202, 209, 248, 85, 128, 2, 17, 0, 0, 0, 9, 55, 203, 48, 136, 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