Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f84fe19948eb32e96394e5ef1743e883906b44a6a39628b9e07b160d8c694d8

Tx prefix hash: 982123a60d4bac882ef49bddd7226d4b579bd69ef71cd9f75317b98da622e4b4
Tx public key: 55ddc22ae8d7bca0b6f36207b03045b4bc1290bb52b94e41f8b9ec4b613e84cb
Timestamp: 1760193496 Timestamp [UCT]: 2025-10-11 14:38:16 Age [y:d:h:m:s]: 00:055:02:15:31
Block: 1387663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39438 RingCT/type: yes/0
Extra: 0155ddc22ae8d7bca0b6f36207b03045b4bc1290bb52b94e41f8b9ec4b613e84cb021100000002163191ee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87eec4b1378cf383213bf3ecb1bbb316723057ee432cd54cba2a39e6d9fa54eb 0.600000000000 1875858 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": 1387673, "vin": [ { "gen": { "height": 1387663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87eec4b1378cf383213bf3ecb1bbb316723057ee432cd54cba2a39e6d9fa54eb" } } ], "extra": [ 1, 85, 221, 194, 42, 232, 215, 188, 160, 182, 243, 98, 7, 176, 48, 69, 180, 188, 18, 144, 187, 82, 185, 78, 65, 248, 185, 236, 75, 97, 62, 132, 203, 2, 17, 0, 0, 0, 2, 22, 49, 145, 238, 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