Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 490b5d90acedb84a879840c4f6978ea1b3e603158d06ea7cd939a24500c38503

Tx prefix hash: b62e0f53a18c1ad035229d9d9012d5f4b11064209345b682dcbe54b0bbf6234c
Tx public key: 647217c93d2b34627fb49090885f9e953e312158cf7659dd9607c0e48f791af1
Timestamp: 1752932729 Timestamp [UCT]: 2025-07-19 13:45:29 Age [y:d:h:m:s]: 00:125:10:36:06
Block: 1328864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88440 RingCT/type: yes/0
Extra: 01647217c93d2b34627fb49090885f9e953e312158cf7659dd9607c0e48f791af1021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc6c806f68d611b2d33c89b8721c491d2ce3843b1313ede34aabaae5852f08b2 0.600000000000 1816637 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": 1328874, "vin": [ { "gen": { "height": 1328864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc6c806f68d611b2d33c89b8721c491d2ce3843b1313ede34aabaae5852f08b2" } } ], "extra": [ 1, 100, 114, 23, 201, 61, 43, 52, 98, 127, 180, 144, 144, 136, 95, 158, 149, 62, 49, 33, 88, 207, 118, 89, 221, 150, 7, 192, 228, 143, 121, 26, 241, 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