Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87d1950328aaef462e1d7669f82dae4f91ede95c2c19b04f410e812996feac0f

Tx prefix hash: 2c341923f9f47adcf136e10a750707349b9f802028ec9adbd3c329ec929abfef
Tx public key: e83cbc936c3a73c16d0315a974ce5a8f244d53409eef50831ee34430d1fa7296
Timestamp: 1760591625 Timestamp [UCT]: 2025-10-16 05:13:45 Age [y:d:h:m:s]: 00:079:14:26:29
Block: 1390967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57002 RingCT/type: yes/0
Extra: 01e83cbc936c3a73c16d0315a974ce5a8f244d53409eef50831ee34430d1fa72960211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a904f06889839d1a6df14de35f251759f372f05914b9b42f81c676a9c6d9cfa 0.600000000000 1879214 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": 1390977, "vin": [ { "gen": { "height": 1390967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a904f06889839d1a6df14de35f251759f372f05914b9b42f81c676a9c6d9cfa" } } ], "extra": [ 1, 232, 60, 188, 147, 108, 58, 115, 193, 109, 3, 21, 169, 116, 206, 90, 143, 36, 77, 83, 64, 158, 239, 80, 131, 30, 227, 68, 48, 209, 250, 114, 150, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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