Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6bcb8fec55561db181fae84b741edc7e6be685f2961be458d260b4e20c36533

Tx prefix hash: 62774f1feba42aedfd4fe59743ac2ab2eb99c6571625eeb2d39a4d10f6b72b35
Tx public key: ab318da1f70a4bfaa0a9a4a3dbcc4d89b4a82012ab233ebeab0b34314262be3e
Timestamp: 1702815920 Timestamp [UCT]: 2023-12-17 12:25:20 Age [y:d:h:m:s]: 01:034:04:30:33
Block: 915082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285757 RingCT/type: yes/0
Extra: 01ab318da1f70a4bfaa0a9a4a3dbcc4d89b4a82012ab233ebeab0b34314262be3e021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae64e377f7413e6f854b2521250e63df7e2d631013b27736019e7c63e493f484 0.600000000000 1372464 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": 915092, "vin": [ { "gen": { "height": 915082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae64e377f7413e6f854b2521250e63df7e2d631013b27736019e7c63e493f484" } } ], "extra": [ 1, 171, 49, 141, 161, 247, 10, 75, 250, 160, 169, 164, 163, 219, 204, 77, 137, 180, 168, 32, 18, 171, 35, 62, 190, 171, 11, 52, 49, 66, 98, 190, 62, 2, 17, 0, 0, 0, 2, 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