Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27c370f0d926ac7ab9b92698df822e9926a992b28b9e42212a00631d250d2573

Tx prefix hash: 3827e28b7b004d93e0e559ced0de5080a6a09e783725008a72eb55e4895a2ff0
Tx public key: f1bf342df59f0ff8bbdd20d1a31d8beddd78f46276b9b7fea439eeb4a502da87
Timestamp: 1731921839 Timestamp [UCT]: 2024-11-18 09:23:59 Age [y:d:h:m:s]: 00:142:15:38:09
Block: 1156297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101776 RingCT/type: yes/0
Extra: 01f1bf342df59f0ff8bbdd20d1a31d8beddd78f46276b9b7fea439eeb4a502da87021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f379dcb4b3aec9fa411a8d9c196dfe8d923145e55df1dcecc52462170e5988d 0.600000000000 1641920 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": 1156307, "vin": [ { "gen": { "height": 1156297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f379dcb4b3aec9fa411a8d9c196dfe8d923145e55df1dcecc52462170e5988d" } } ], "extra": [ 1, 241, 191, 52, 45, 245, 159, 15, 248, 187, 221, 32, 209, 163, 29, 139, 237, 221, 120, 244, 98, 118, 185, 183, 254, 164, 57, 238, 180, 165, 2, 218, 135, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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