Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d49a9a8391fc3944a074fb69826327ec3ffb5613eb7620f5e195dceea002a4

Tx prefix hash: 3589e608b71370be3a1b18932afd9cf3d1149223238f96212c05d58ee271f795
Tx public key: 2546ef4ec4a5a9df449dd3ac97562db8bd0cb6fccde4ea1d33e28137128a7fa5
Timestamp: 1750104231 Timestamp [UCT]: 2025-06-16 20:03:51 Age [y:d:h:m:s]: 00:156:10:47:03
Block: 1306456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109610 RingCT/type: yes/0
Extra: 012546ef4ec4a5a9df449dd3ac97562db8bd0cb6fccde4ea1d33e28137128a7fa5021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e31f51e027a9b14375f2771a42dd729df8cbd760202a56ecafb6872b53e30272 0.600000000000 1794063 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": 1306466, "vin": [ { "gen": { "height": 1306456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e31f51e027a9b14375f2771a42dd729df8cbd760202a56ecafb6872b53e30272" } } ], "extra": [ 1, 37, 70, 239, 78, 196, 165, 169, 223, 68, 157, 211, 172, 151, 86, 45, 184, 189, 12, 182, 252, 205, 228, 234, 29, 51, 226, 129, 55, 18, 138, 127, 165, 2, 17, 0, 0, 0, 2, 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