Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b31d3f3e5410e2f4a9988e6a43eb4724c44a6a6cb9319a8bb5e7ff515bdbab1

Tx prefix hash: b6e9c0faf8853ac2696fc93cffc8ca2f22a61dda82417ae28278fc931be673f4
Tx public key: c024716d5a84f9bab85b3badb77582f58153fc31770070d4f09267cee51864f3
Timestamp: 1736341213 Timestamp [UCT]: 2025-01-08 13:00:13 Age [y:d:h:m:s]: 00:105:03:38:09
Block: 1192892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74940 RingCT/type: yes/0
Extra: 01c024716d5a84f9bab85b3badb77582f58153fc31770070d4f09267cee51864f3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab438b086840c3fb4b9f10a9e3da39e3917ba6f75b5bdcfb557295f7b5a94c5a 0.600000000000 1679449 of 15

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": 1192902, "vin": [ { "gen": { "height": 1192892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab438b086840c3fb4b9f10a9e3da39e3917ba6f75b5bdcfb557295f7b5a94c5a" } } ], "extra": [ 1, 192, 36, 113, 109, 90, 132, 249, 186, 184, 91, 59, 173, 183, 117, 130, 245, 129, 83, 252, 49, 119, 0, 112, 212, 240, 146, 103, 206, 229, 24, 100, 243, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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