Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d38c15b0cc1df6a975979e34658d6a71b20f2527f4eb017cedea03b96ac5364d

Tx prefix hash: a1bc7514ae055bc8d4bb0b55951ee3b495f94d95d7f05fbdc188221b6d241532
Tx public key: 60f0c6e3dcb8a23cc8bfc3acf7b861504ef8d995f4f78399a1cb774e90224761
Timestamp: 1740742023 Timestamp [UCT]: 2025-02-28 11:27:03 Age [y:d:h:m:s]: 00:335:16:21:38
Block: 1229046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237593 RingCT/type: yes/0
Extra: 0160f0c6e3dcb8a23cc8bfc3acf7b861504ef8d995f4f78399a1cb774e902247610211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35b361aadd37bac979593aac69aac163525ad449b9ff3ecd9328ac5868da6a90 0.600000000000 1715927 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": 1229056, "vin": [ { "gen": { "height": 1229046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35b361aadd37bac979593aac69aac163525ad449b9ff3ecd9328ac5868da6a90" } } ], "extra": [ 1, 96, 240, 198, 227, 220, 184, 162, 60, 200, 191, 195, 172, 247, 184, 97, 80, 78, 248, 217, 149, 244, 247, 131, 153, 161, 203, 119, 78, 144, 34, 71, 97, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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