Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 223a88f35adc2c77b41c05494eff22ba8a2ef60282813be80242d44dd2a2a382

Tx prefix hash: f9d68d122f9593814f2c06fc5b9a7ef382a3e4de4d28f60752656183d814b2c9
Tx public key: 9f9edc1620a4341932cf5ac69a2b8802fc1fb0a8dccf832e613f3244e083e37d
Timestamp: 1716923767 Timestamp [UCT]: 2024-05-28 19:16:07 Age [y:d:h:m:s]: 00:310:06:54:25
Block: 1032062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221746 RingCT/type: yes/0
Extra: 019f9edc1620a4341932cf5ac69a2b8802fc1fb0a8dccf832e613f3244e083e37d02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d324a09fdf9030cbbc243f8d9e5ab488257024dc0da508c5fd0c4e625056afd7 0.600000000000 1500511 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": 1032072, "vin": [ { "gen": { "height": 1032062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d324a09fdf9030cbbc243f8d9e5ab488257024dc0da508c5fd0c4e625056afd7" } } ], "extra": [ 1, 159, 158, 220, 22, 32, 164, 52, 25, 50, 207, 90, 198, 154, 43, 136, 2, 252, 31, 176, 168, 220, 207, 131, 46, 97, 63, 50, 68, 224, 131, 227, 125, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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