Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb0a34fe55e6ccc4e707161ac7bb3b4eb84a22601f0928d953207690a6f1a2ee

Tx prefix hash: fd62669401e4760824b0d91ba814ce0e8cd27a9004138293b7bd6dc4fd29be01
Tx public key: 0ea8df81be6397489f32dbfee5a4a6f665a8019d404c096b8be32d809739ac40
Timestamp: 1713060573 Timestamp [UCT]: 2024-04-14 02:09:33 Age [y:d:h:m:s]: 01:025:20:12:28
Block: 1000007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279443 RingCT/type: yes/0
Extra: 010ea8df81be6397489f32dbfee5a4a6f665a8019d404c096b8be32d809739ac40021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b17bd2830dda5b4a1aeb217358f959c33d6cc0b8dbfd58984298153687265de 0.600000000000 1460495 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": 1000017, "vin": [ { "gen": { "height": 1000007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b17bd2830dda5b4a1aeb217358f959c33d6cc0b8dbfd58984298153687265de" } } ], "extra": [ 1, 14, 168, 223, 129, 190, 99, 151, 72, 159, 50, 219, 254, 229, 164, 166, 246, 101, 168, 1, 157, 64, 76, 9, 107, 139, 227, 45, 128, 151, 57, 172, 64, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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