Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18c0e259c4a823069816d672c24044cb73ac2cd268beb6343cb00d67b1bec01c

Tx prefix hash: 1552fa5f1c7673edd8c45e87f1a48a3a43408dd7646ea92333758a42ab664cbe
Tx public key: 602463b5499fa9e864f4aa7b80862d2cea3b7b948f96745f941a648df7f7edc4
Timestamp: 1749704485 Timestamp [UCT]: 2025-06-12 05:01:25 Age [y:d:h:m:s]: 00:151:11:07:35
Block: 1303230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105967 RingCT/type: yes/0
Extra: 01602463b5499fa9e864f4aa7b80862d2cea3b7b948f96745f941a648df7f7edc4021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a2566be69cfac3c8e28a24c11f875a771a6ec23546d22f5506fa3b73cdea154 0.600000000000 1790807 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": 1303240, "vin": [ { "gen": { "height": 1303230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a2566be69cfac3c8e28a24c11f875a771a6ec23546d22f5506fa3b73cdea154" } } ], "extra": [ 1, 96, 36, 99, 181, 73, 159, 169, 232, 100, 244, 170, 123, 128, 134, 45, 44, 234, 59, 123, 148, 143, 150, 116, 95, 148, 26, 100, 141, 247, 247, 237, 196, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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