Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f38f6c5f848be44f8130d4d3dc43acdec972f4755aa9c45cba9c241c434f9f

Tx prefix hash: e8cbd4b028c7737e18b24932d1e056fc341a84cc60b29a756b5e863bf00357d2
Tx public key: 11a8b07df73a2476601881a38e873482e52c3088aead38b17350f52119a45ed0
Timestamp: 1700815311 Timestamp [UCT]: 2023-11-24 08:41:51 Age [y:d:h:m:s]: 01:136:02:58:18
Block: 898503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358453 RingCT/type: yes/0
Extra: 0111a8b07df73a2476601881a38e873482e52c3088aead38b17350f52119a45ed002110000000975e3f0e9000000000000000000

1 output(s) for total of 0.646973601000 dcy

stealth address amount amount idx
00: 1cbd007ecf1a62a32862376ad954a505e54fb0ef388304ba768748d537fe1996 0.646973601000 1354924 of 0

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": 898513, "vin": [ { "gen": { "height": 898503 } } ], "vout": [ { "amount": 646973601, "target": { "key": "1cbd007ecf1a62a32862376ad954a505e54fb0ef388304ba768748d537fe1996" } } ], "extra": [ 1, 17, 168, 176, 125, 247, 58, 36, 118, 96, 24, 129, 163, 142, 135, 52, 130, 229, 44, 48, 136, 174, 173, 56, 177, 115, 80, 245, 33, 25, 164, 94, 208, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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