Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdcb89472f1e02d4cc916cd9388973bb11dccda372e5c9e7cd5c263435ee01b1

Tx prefix hash: 838e3e764583d3d8948c4661a33edeb62b672c503c85125892381c26a11293eb
Tx public key: 441cde0e4077b720bf6107aea53b7b51c1dd9d4150f5b8826b950ef8433e8a4f
Timestamp: 1750083908 Timestamp [UCT]: 2025-06-16 14:25:08 Age [y:d:h:m:s]: 00:150:18:53:48
Block: 1306295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105556 RingCT/type: yes/0
Extra: 01441cde0e4077b720bf6107aea53b7b51c1dd9d4150f5b8826b950ef8433e8a4f02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b621c89bc9ad3650fd8232655f454e184d9d9bbfe8d9f4c2048ed23eb6c0e99 0.600000000000 1793900 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": 1306305, "vin": [ { "gen": { "height": 1306295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b621c89bc9ad3650fd8232655f454e184d9d9bbfe8d9f4c2048ed23eb6c0e99" } } ], "extra": [ 1, 68, 28, 222, 14, 64, 119, 183, 32, 191, 97, 7, 174, 165, 59, 123, 81, 193, 221, 157, 65, 80, 245, 184, 130, 107, 149, 14, 248, 67, 62, 138, 79, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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