Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36ad1ac3affc94c27a6a2e8c959dd4ca7ddcd8fd100431eb0d582e6ced524ea2

Tx prefix hash: 2749173fae7f08411ab4c83ee46b94f3d45160fc78b0a8ef71e628998d34acdb
Tx public key: cad293dd56c55cd38e2a0a3455ed09fd034302e9c5e0cd6193eede9b89cddc7a
Timestamp: 1715153770 Timestamp [UCT]: 2024-05-08 07:36:10 Age [y:d:h:m:s]: 01:189:08:47:18
Block: 1017388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393953 RingCT/type: yes/0
Extra: 01cad293dd56c55cd38e2a0a3455ed09fd034302e9c5e0cd6193eede9b89cddc7a0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d2e132e643542b8398634b6011587fda507d5ba4a89bc045dec34a2baa4fa9d 0.600000000000 1481171 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": 1017398, "vin": [ { "gen": { "height": 1017388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d2e132e643542b8398634b6011587fda507d5ba4a89bc045dec34a2baa4fa9d" } } ], "extra": [ 1, 202, 210, 147, 221, 86, 197, 92, 211, 142, 42, 10, 52, 85, 237, 9, 253, 3, 67, 2, 233, 197, 224, 205, 97, 147, 238, 222, 155, 137, 205, 220, 122, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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