Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f407302ab307342172a3da48de3fc0a988fca52bc2935ec52b6f649b9dec91dd

Tx prefix hash: b5d8b10cedca0b6608e02a1af96c9dd28eecb0d65bdd49396fb9205226210ed8
Tx public key: 61716626a184e9f26cbb80382209ce9b929ca691fc726caca5cba8a10490a3c2
Timestamp: 1705290893 Timestamp [UCT]: 2024-01-15 03:54:53 Age [y:d:h:m:s]: 01:086:04:39:23
Block: 935579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322720 RingCT/type: yes/0
Extra: 0161716626a184e9f26cbb80382209ce9b929ca691fc726caca5cba8a10490a3c202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3ad2d6754a62b6bc76086a2c1cb29bc5b5d26a4ce40e8f5950dafe3ddb582d4 0.600000000000 1393595 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": 935589, "vin": [ { "gen": { "height": 935579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3ad2d6754a62b6bc76086a2c1cb29bc5b5d26a4ce40e8f5950dafe3ddb582d4" } } ], "extra": [ 1, 97, 113, 102, 38, 161, 132, 233, 242, 108, 187, 128, 56, 34, 9, 206, 155, 146, 156, 166, 145, 252, 114, 108, 172, 165, 203, 168, 161, 4, 144, 163, 194, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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