Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a8883bda624610a35a4ebbadf51c06936f65e63d63deaf1779b60ecaa73d67c

Tx prefix hash: 71077c121e17cb085ed09b1f9d5bc68a23940605f06c2856ee9efc7b0f60c14c
Tx public key: 7f465960c0c80d4aa0d0967002914b5f2571cc95bbc9c79b01b69111564f8b6d
Timestamp: 1712683380 Timestamp [UCT]: 2024-04-09 17:23:00 Age [y:d:h:m:s]: 01:028:08:29:15
Block: 996876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281250 RingCT/type: yes/0
Extra: 017f465960c0c80d4aa0d0967002914b5f2571cc95bbc9c79b01b69111564f8b6d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d0001075067e02b65698ad1771d29251e9138e177742b95fc8cfd4ece7b956 0.600000000000 1457304 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": 996886, "vin": [ { "gen": { "height": 996876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d0001075067e02b65698ad1771d29251e9138e177742b95fc8cfd4ece7b956" } } ], "extra": [ 1, 127, 70, 89, 96, 192, 200, 13, 74, 160, 208, 150, 112, 2, 145, 75, 95, 37, 113, 204, 149, 187, 201, 199, 155, 1, 182, 145, 17, 86, 79, 139, 109, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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