Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2cdc5b3bf0040a1dd931d415cdab35972d14806357dc73ef1e045eab5191ae2

Tx prefix hash: 395c0f5ce932a760209a12325543ddc62813741c64d124c3dfb4baa6f78aafd8
Tx public key: 08d711943f1c347a5770c0a99e72a9e9c8531dedc1cb7baa9f94374b3e4aa095
Timestamp: 1726898284 Timestamp [UCT]: 2024-09-21 05:58:04 Age [y:d:h:m:s]: 00:266:04:34:05
Block: 1114746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190036 RingCT/type: yes/0
Extra: 0108d711943f1c347a5770c0a99e72a9e9c8531dedc1cb7baa9f94374b3e4aa09502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f59ff58ffd0ae9065c7a0eeeaca3f93519c3ef0b7d4daab50e5e27f28b9bff95 0.600000000000 1594635 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": 1114756, "vin": [ { "gen": { "height": 1114746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f59ff58ffd0ae9065c7a0eeeaca3f93519c3ef0b7d4daab50e5e27f28b9bff95" } } ], "extra": [ 1, 8, 215, 17, 148, 63, 28, 52, 122, 87, 112, 192, 169, 158, 114, 169, 233, 200, 83, 29, 237, 193, 203, 123, 170, 159, 148, 55, 75, 62, 74, 160, 149, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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