Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bc8d2845cd4083eb2e62bbe08f6f632617ce6895d7b642474712331489e3afe

Tx prefix hash: c6fa7e13310dc0b6813dedaed5b831098b4ccfbf03499603daf4d4fe7b1af801
Tx public key: 2c082b8b7d66748c983d164fe918c7996a84f5e0a19241f2cacf186e842774f9
Timestamp: 1696323302 Timestamp [UCT]: 2023-10-03 08:55:02 Age [y:d:h:m:s]: 01:186:04:46:35
Block: 861468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394109 RingCT/type: yes/0
Extra: 012c082b8b7d66748c983d164fe918c7996a84f5e0a19241f2cacf186e842774f9021100000007faf35c9c000000000000000000

1 output(s) for total of 0.858220617000 dcy

stealth address amount amount idx
00: ddd7ea300d64e7c9f6ccce2a3ae2ab0eed3d1104129a0d1fad9570d278e4c964 0.858220617000 1315812 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": 861478, "vin": [ { "gen": { "height": 861468 } } ], "vout": [ { "amount": 858220617, "target": { "key": "ddd7ea300d64e7c9f6ccce2a3ae2ab0eed3d1104129a0d1fad9570d278e4c964" } } ], "extra": [ 1, 44, 8, 43, 139, 125, 102, 116, 140, 152, 61, 22, 79, 233, 24, 199, 153, 106, 132, 245, 224, 161, 146, 65, 242, 202, 207, 24, 110, 132, 39, 116, 249, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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