Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404ba86ee70811f63e548140b675afc58dc91e5ff6a26528eb143981d24a008b

Tx prefix hash: 02dbce34e9530f75d265e09accf41a5425d605d5c34aac2f27c6f272d07407ce
Tx public key: 7f81d63b7127d61d0f43589612b3fc9570e8b3624153edc7281e0fce46a01b8d
Timestamp: 1744517430 Timestamp [UCT]: 2025-04-13 04:10:30 Age [y:d:h:m:s]: 00:211:21:04:23
Block: 1260309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149146 RingCT/type: yes/0
Extra: 017f81d63b7127d61d0f43589612b3fc9570e8b3624153edc7281e0fce46a01b8d02110000000d6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae245b3c1f5a2c20740ca7bf6f4f4f5784d20149c5588d171c178f6010ed0e1f 0.600000000000 1747464 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": 1260319, "vin": [ { "gen": { "height": 1260309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae245b3c1f5a2c20740ca7bf6f4f4f5784d20149c5588d171c178f6010ed0e1f" } } ], "extra": [ 1, 127, 129, 214, 59, 113, 39, 214, 29, 15, 67, 88, 150, 18, 179, 252, 149, 112, 232, 179, 98, 65, 83, 237, 199, 40, 30, 15, 206, 70, 160, 27, 141, 2, 17, 0, 0, 0, 13, 108, 152, 170, 61, 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