Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8811768c1e02b48194db3f8a649a81bb599d4cb49eb6963bdb0626b004804e

Tx prefix hash: e44fd2d0918298eafb10910ca2f3ff6acaf65c98924a8a63700b4b8bc3a4bce4
Tx public key: 56e682aac3ac19496eb44a3c9de3d4eaf7c688c33b4dcbd9fa6ddf9b469103b4
Timestamp: 1765283772 Timestamp [UCT]: 2025-12-09 12:36:12 Age [y:d:h:m:s]: 00:031:02:34:15
Block: 1429837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22288 RingCT/type: yes/0
Extra: 0156e682aac3ac19496eb44a3c9de3d4eaf7c688c33b4dcbd9fa6ddf9b469103b402110000000d70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cf3403ee9e4aadef7b7dde10df1870f7306f7e055c45a2a7404c067ae59e3f6 0.600000000000 1918568 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": 1429847, "vin": [ { "gen": { "height": 1429837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cf3403ee9e4aadef7b7dde10df1870f7306f7e055c45a2a7404c067ae59e3f6" } } ], "extra": [ 1, 86, 230, 130, 170, 195, 172, 25, 73, 110, 180, 74, 60, 157, 227, 212, 234, 247, 198, 136, 195, 59, 77, 203, 217, 250, 109, 223, 155, 70, 145, 3, 180, 2, 17, 0, 0, 0, 13, 112, 96, 157, 3, 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