Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9da1c1e81b2bb31124bf6bedd5ea91a1f78e001078c6f284e5b681910f15cc1c

Tx prefix hash: 180540275051e1a13402de44798006fd852cc06a6eecc093b96649038245573c
Tx public key: 4e8634e3936ea9d53d5b7bce24c44df2e8b02022695e321b617d3e4acd6e8e8a
Timestamp: 1578923999 Timestamp [UCT]: 2020-01-13 13:59:59 Age [y:d:h:m:s]: 04:362:22:05:45
Block: 44671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148916 RingCT/type: yes/0
Extra: 014e8634e3936ea9d53d5b7bce24c44df2e8b02022695e321b617d3e4acd6e8e8a02110000000717786bcf000000000000000000

1 output(s) for total of 436.503041312000 dcy

stealth address amount amount idx
00: cb36f8c80d8184addc15d128e875d95ea31281e74cda09ee8045ce14c9847896 436.503041312000 81366 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": 44681, "vin": [ { "gen": { "height": 44671 } } ], "vout": [ { "amount": 436503041312, "target": { "key": "cb36f8c80d8184addc15d128e875d95ea31281e74cda09ee8045ce14c9847896" } } ], "extra": [ 1, 78, 134, 52, 227, 147, 110, 169, 213, 61, 91, 123, 206, 36, 196, 77, 242, 232, 176, 32, 34, 105, 94, 50, 27, 97, 125, 62, 74, 205, 110, 142, 138, 2, 17, 0, 0, 0, 7, 23, 120, 107, 207, 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