Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7f89fbf7c182105715c1c010a66aa5940bca7d3d8f0d769fc4524beb98448d2

Tx prefix hash: 22faf5b2a407cec9336165010ea8fdd75c73848f45c0b429355949d8690efd49
Tx public key: bb6effb5d4f98af8081b5538dcb9977f2728aa490406f2763a8ed47c4552be09
Timestamp: 1733616142 Timestamp [UCT]: 2024-12-08 00:02:22 Age [y:d:h:m:s]: 00:117:23:41:35
Block: 1170344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84112 RingCT/type: yes/0
Extra: 01bb6effb5d4f98af8081b5538dcb9977f2728aa490406f2763a8ed47c4552be090211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 297c255c6389d6523a7b491db0b4b1d9ae7a4f7d25bed5415075eb3adafe311a 0.600000000000 1656073 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": 1170354, "vin": [ { "gen": { "height": 1170344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "297c255c6389d6523a7b491db0b4b1d9ae7a4f7d25bed5415075eb3adafe311a" } } ], "extra": [ 1, 187, 110, 255, 181, 212, 249, 138, 248, 8, 27, 85, 56, 220, 185, 151, 127, 39, 40, 170, 73, 4, 6, 242, 118, 58, 142, 212, 124, 69, 82, 190, 9, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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