Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae5092b7cdfde4d6d415ce3cd140a259595fc66a156018c542c6e63985a4c8ac

Tx prefix hash: ee10eb4611ff4eb38cd201a59f843771eab0c7f190b6a3d6eee59051c6dc4623
Tx public key: e99c9f78f00253d35395a56059d7d76a44c00a1035d8f26ae6e999486ef165b5
Timestamp: 1737536608 Timestamp [UCT]: 2025-01-22 09:03:28 Age [y:d:h:m:s]: 00:303:13:27:33
Block: 1202745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214507 RingCT/type: yes/0
Extra: 01e99c9f78f00253d35395a56059d7d76a44c00a1035d8f26ae6e999486ef165b50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f5715d914bee3ac5c4e5abd4c4c7b58cfa2af3b2cca8bf16c74df452f2d20cc 0.600000000000 1689410 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": 1202755, "vin": [ { "gen": { "height": 1202745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f5715d914bee3ac5c4e5abd4c4c7b58cfa2af3b2cca8bf16c74df452f2d20cc" } } ], "extra": [ 1, 233, 156, 159, 120, 240, 2, 83, 211, 83, 149, 165, 96, 89, 215, 215, 106, 68, 192, 10, 16, 53, 216, 242, 106, 230, 233, 153, 72, 110, 241, 101, 181, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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