Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63cdc7f4cb7d0f161644914240c2ebc3d32031d9f9a7aeba00f8abf10136cf96

Tx prefix hash: 0e098cb0455e7b82a86d89609bf3c36afae17ded007b434fc430e06a12cb8b2e
Tx public key: 1cf9ab938158ed0cb1dc9dc61734ebeac21fcde945a8d8bb43d7d95a00683885
Timestamp: 1696322546 Timestamp [UCT]: 2023-10-03 08:42:26 Age [y:d:h:m:s]: 01:106:04:19:00
Block: 861459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337164 RingCT/type: yes/0
Extra: 011cf9ab938158ed0cb1dc9dc61734ebeac21fcde945a8d8bb43d7d95a00683885021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.858469549000 dcy

stealth address amount amount idx
00: 6763e2671446a180a56bcb959be93228be930840c60fd12572164065347b5831 0.858469549000 1315801 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": 861469, "vin": [ { "gen": { "height": 861459 } } ], "vout": [ { "amount": 858469549, "target": { "key": "6763e2671446a180a56bcb959be93228be930840c60fd12572164065347b5831" } } ], "extra": [ 1, 28, 249, 171, 147, 129, 88, 237, 12, 177, 220, 157, 198, 23, 52, 235, 234, 194, 31, 205, 233, 69, 168, 216, 187, 67, 215, 217, 90, 0, 104, 56, 133, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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