Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d548203cad1424c7b994b1d5db6d23f289c85d2b12f32e916fc09a46d8dbe3bf

Tx prefix hash: 123012254fe68218951898afc2b52da043c6a8b682770b4eca918aa3aff0450b
Tx public key: 0804d4e841ede6b7705777e0531b9b1a06e9bf4645bbd7ec428e14d9e500402f
Timestamp: 1702208530 Timestamp [UCT]: 2023-12-10 11:42:10 Age [y:d:h:m:s]: 01:037:05:08:18
Block: 910059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287943 RingCT/type: yes/0
Extra: 010804d4e841ede6b7705777e0531b9b1a06e9bf4645bbd7ec428e14d9e500402f02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f9a629759f429df671787d02b403ad8232fb9e0dd4c30545a5c0e50f705c1cc 0.600000000000 1367200 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": 910069, "vin": [ { "gen": { "height": 910059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f9a629759f429df671787d02b403ad8232fb9e0dd4c30545a5c0e50f705c1cc" } } ], "extra": [ 1, 8, 4, 212, 232, 65, 237, 230, 183, 112, 87, 119, 224, 83, 27, 155, 26, 6, 233, 191, 70, 69, 187, 215, 236, 66, 142, 20, 217, 229, 0, 64, 47, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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