Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c3a3dd1c43c2a0a5fccae8a41b281caec4a4d5b34840465187e13e2df20fe23

Tx prefix hash: 04f91c19f9323e544b1612d0dec05b2758909a6bc2abfff1deb46c74c7043334
Tx public key: 9d8fbce51efb6b29346e4b9f7a2a01b9a1309e96811adad64dfe69d1a6a4c374
Timestamp: 1764368048 Timestamp [UCT]: 2025-11-28 22:14:08 Age [y:d:h:m:s]: 00:029:05:37:23
Block: 1422260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20939 RingCT/type: yes/0
Extra: 019d8fbce51efb6b29346e4b9f7a2a01b9a1309e96811adad64dfe69d1a6a4c37402110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36bbf23713ff654b32c022e38191d8be6ce7fbf64ebb461e5cb4be952d763f2c 0.600000000000 1910825 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": 1422270, "vin": [ { "gen": { "height": 1422260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36bbf23713ff654b32c022e38191d8be6ce7fbf64ebb461e5cb4be952d763f2c" } } ], "extra": [ 1, 157, 143, 188, 229, 30, 251, 107, 41, 52, 110, 75, 159, 122, 42, 1, 185, 161, 48, 158, 150, 129, 26, 218, 214, 77, 254, 105, 209, 166, 164, 195, 116, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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