Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda83c23cd864ea8dcf5c1219a946d5cc8a8e9c8ca3d9a11d27962689ba4d3bb

Tx prefix hash: 1bab51742d8a0d31b6fb7f7e9be9613920d8a5100600443e28103d0a438dae13
Tx public key: b6a513a61619184c810b0cf33d69dae2a6a78180ff3137a68068d8421c8df0c9
Timestamp: 1581255936 Timestamp [UCT]: 2020-02-09 13:45:36 Age [y:d:h:m:s]: 04:319:13:36:40
Block: 61435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120454 RingCT/type: yes/0
Extra: 01b6a513a61619184c810b0cf33d69dae2a6a78180ff3137a68068d8421c8df0c902110000000d03d36d11000000000000000000

1 output(s) for total of 384.103845123000 dcy

stealth address amount amount idx
00: 4d6a12b3084aa4b25a9ef529dc8802ce436288e85b3f189815a130b66afa87db 384.103845123000 113219 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": 61445, "vin": [ { "gen": { "height": 61435 } } ], "vout": [ { "amount": 384103845123, "target": { "key": "4d6a12b3084aa4b25a9ef529dc8802ce436288e85b3f189815a130b66afa87db" } } ], "extra": [ 1, 182, 165, 19, 166, 22, 25, 24, 76, 129, 11, 12, 243, 61, 105, 218, 226, 166, 167, 129, 128, 255, 49, 55, 166, 128, 104, 216, 66, 28, 141, 240, 201, 2, 17, 0, 0, 0, 13, 3, 211, 109, 17, 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