Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8904ab7b70b7e027408ad394c317d2627fdf7499227f4cfa8f85bc120ddf9e2

Tx prefix hash: e77cf7bacb9e8f9917bffcad14a7b7f3f6c15ad357a92144e4c5c517fb6637c7
Tx public key: 56626b89581de8b1cdcc425eb93763abcd987ed3291bb30c01929b14e60913c5
Timestamp: 1576924632 Timestamp [UCT]: 2019-12-21 10:37:12 Age [y:d:h:m:s]: 05:085:01:39:05
Block: 28810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1210311 RingCT/type: yes/0
Extra: 0156626b89581de8b1cdcc425eb93763abcd987ed3291bb30c01929b14e60913c50211000000068a2ee0d9000000000000000000

1 output(s) for total of 492.653275276000 dcy

stealth address amount amount idx
00: b28f31a8ee61cb285189ec43d18537bebdd7ffe28edbdad34a942a65a6a4811f 492.653275276000 47610 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": 28820, "vin": [ { "gen": { "height": 28810 } } ], "vout": [ { "amount": 492653275276, "target": { "key": "b28f31a8ee61cb285189ec43d18537bebdd7ffe28edbdad34a942a65a6a4811f" } } ], "extra": [ 1, 86, 98, 107, 137, 88, 29, 232, 177, 205, 204, 66, 94, 185, 55, 99, 171, 205, 152, 126, 211, 41, 27, 179, 12, 1, 146, 155, 20, 230, 9, 19, 197, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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