Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c84c4e78318c567421e4e21087ea55c573907e058603c5a0de9a8fc9674146fe

Tx prefix hash: 396540466ece48bf02224ed9fdf384290ce1be38e63e9183ee9b64e15519959f
Tx public key: 9443c7dcb5c97fda2c05c0d70a4f42e1a1df55953850618054efd3f5c816ee28
Timestamp: 1735642224 Timestamp [UCT]: 2024-12-31 10:50:24 Age [y:d:h:m:s]: 00:314:06:28:07
Block: 1187106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222115 RingCT/type: yes/0
Extra: 019443c7dcb5c97fda2c05c0d70a4f42e1a1df55953850618054efd3f5c816ee280211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45027683c15b485a472c0ac7d327c3bb0206392db393f316cafd8bae6f3cdc70 0.600000000000 1673593 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": 1187116, "vin": [ { "gen": { "height": 1187106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45027683c15b485a472c0ac7d327c3bb0206392db393f316cafd8bae6f3cdc70" } } ], "extra": [ 1, 148, 67, 199, 220, 181, 201, 127, 218, 44, 5, 192, 215, 10, 79, 66, 225, 161, 223, 85, 149, 56, 80, 97, 128, 84, 239, 211, 245, 200, 22, 238, 40, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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