Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb1c63cb944dd8da9f32f50c03a9c89631fa07451f2844ffa0c0b73223361c6

Tx prefix hash: 14eec5f7672eae14f51628a59d62b3083c595adada8cece2d50c4f089681c780
Tx public key: 03b915277ef21e66e3a1900990e7bf7e7c25ed681d4dcf825f60aeae23887605
Timestamp: 1731429269 Timestamp [UCT]: 2024-11-12 16:34:29 Age [y:d:h:m:s]: 00:132:17:02:10
Block: 1152213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94671 RingCT/type: yes/0
Extra: 0103b915277ef21e66e3a1900990e7bf7e7c25ed681d4dcf825f60aeae238876050211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d99108c81bbe64bcd8f824c0ecde7204c8688be2f0116c40b0a50a6de164883e 0.600000000000 1637804 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": 1152223, "vin": [ { "gen": { "height": 1152213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d99108c81bbe64bcd8f824c0ecde7204c8688be2f0116c40b0a50a6de164883e" } } ], "extra": [ 1, 3, 185, 21, 39, 126, 242, 30, 102, 227, 161, 144, 9, 144, 231, 191, 126, 124, 37, 237, 104, 29, 77, 207, 130, 95, 96, 174, 174, 35, 136, 118, 5, 2, 17, 0, 0, 0, 2, 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