Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990bd4f097428f1b5b8cf6c03de18d2f99d076b0c9f8b1aacefa34f34ee8f001

Tx prefix hash: d77f03323d5719775b9aa0188091365049c97d1f3b4fb7d53e24f68b14eac5fc
Tx public key: 2bdbf47976842213d0277498c5f13af8b6cb0384fd5d19764048b311c4e36704
Timestamp: 1765897963 Timestamp [UCT]: 2025-12-16 15:12:43 Age [y:d:h:m:s]: 00:017:23:41:44
Block: 1434928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12897 RingCT/type: yes/0
Extra: 012bdbf47976842213d0277498c5f13af8b6cb0384fd5d19764048b311c4e3670402110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62a0b19008547ac778e86d1737c3f83ffd0e10beb1eaa3ffce6f9e8d96857322 0.600000000000 1923725 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": 1434938, "vin": [ { "gen": { "height": 1434928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62a0b19008547ac778e86d1737c3f83ffd0e10beb1eaa3ffce6f9e8d96857322" } } ], "extra": [ 1, 43, 219, 244, 121, 118, 132, 34, 19, 208, 39, 116, 152, 197, 241, 58, 248, 182, 203, 3, 132, 253, 93, 25, 118, 64, 72, 179, 17, 196, 227, 103, 4, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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