Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2474c984d2b1815d20aa631847ddfa743d49bbe2a3fd23f6b1de370648827271

Tx prefix hash: c7b145c89280221d5875551fc657abe6b7d252cf4c87e616e0634614a5b7a606
Tx public key: 8f089ca8f775c88c562dc0982a88154b7c74dc2b8fe647a1b6d575977b2193f0
Timestamp: 1765683360 Timestamp [UCT]: 2025-12-14 03:36:00 Age [y:d:h:m:s]: 00:049:07:36:57
Block: 1433147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35140 RingCT/type: yes/0
Extra: 018f089ca8f775c88c562dc0982a88154b7c74dc2b8fe647a1b6d575977b2193f0021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fac031bad04e1187fc6452099fe35c83982a5f5b5060d1623008f69be0a6ee82 0.600000000000 1921926 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": 1433157, "vin": [ { "gen": { "height": 1433147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac031bad04e1187fc6452099fe35c83982a5f5b5060d1623008f69be0a6ee82" } } ], "extra": [ 1, 143, 8, 156, 168, 247, 117, 200, 140, 86, 45, 192, 152, 42, 136, 21, 75, 124, 116, 220, 43, 143, 230, 71, 161, 182, 213, 117, 151, 123, 33, 147, 240, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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