Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5445a06e27666eb8a8c3e66bc7cec9b2cd53fe7832f4739bb28a05e26496af

Tx prefix hash: d4e5341ce69c61ecdf15d9a45892d203e12fd2768300cab7d7180d6aabacaf4d
Tx public key: 3bfc85149a7e52dc9d35ba040ce855caab7ced2f956f85b6f4d6f630fb2b0b0d
Timestamp: 1741409203 Timestamp [UCT]: 2025-03-08 04:46:43 Age [y:d:h:m:s]: 00:257:18:35:29
Block: 1234587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181969 RingCT/type: yes/0
Extra: 013bfc85149a7e52dc9d35ba040ce855caab7ced2f956f85b6f4d6f630fb2b0b0d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb7a7d9f76245767b70ed945f15adf5c7d9fe1e7cd7c928403bf1e862b9fabe4 0.600000000000 1721518 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": 1234597, "vin": [ { "gen": { "height": 1234587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb7a7d9f76245767b70ed945f15adf5c7d9fe1e7cd7c928403bf1e862b9fabe4" } } ], "extra": [ 1, 59, 252, 133, 20, 154, 126, 82, 220, 157, 53, 186, 4, 12, 232, 85, 202, 171, 124, 237, 47, 149, 111, 133, 182, 244, 214, 246, 48, 251, 43, 11, 13, 2, 17, 0, 0, 0, 2, 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