Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca41e86f5998ac4fc1f9a00068961db3b0a251d8552b2d8901be8578983968e5

Tx prefix hash: c06ea74b747e6a023799a02532a9c862aad546ec76cf724e0eb3de9f8b98266a
Tx public key: da0a3bd5f9f1894c48e504ca214113a342e5e70a0297e284f11b217681d26ed8
Timestamp: 1715960360 Timestamp [UCT]: 2024-05-17 15:39:20 Age [y:d:h:m:s]: 00:321:20:18:24
Block: 1024070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230041 RingCT/type: yes/0
Extra: 01da0a3bd5f9f1894c48e504ca214113a342e5e70a0297e284f11b217681d26ed802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba03b2944d1dd9bf260509f425e899ce8f20697e6c5fc88e33bcef3cb3124973 0.600000000000 1489523 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": 1024080, "vin": [ { "gen": { "height": 1024070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba03b2944d1dd9bf260509f425e899ce8f20697e6c5fc88e33bcef3cb3124973" } } ], "extra": [ 1, 218, 10, 59, 213, 249, 241, 137, 76, 72, 229, 4, 202, 33, 65, 19, 163, 66, 229, 231, 10, 2, 151, 226, 132, 241, 27, 33, 118, 129, 210, 110, 216, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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