Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d10ca50f599bc08345add0bcc9d45eeaa49fc8d02eebfdfbc8ecb221d3737db3

Tx prefix hash: c0281165696c3c81a956b986eca950963ad41176028bceb42e38fda8b92319c9
Tx public key: d5f74eb2a22f91c1416a1363661a5cfe2611d0c214492c857fe51b502e120e78
Timestamp: 1729017732 Timestamp [UCT]: 2024-10-15 18:42:12 Age [y:d:h:m:s]: 01:062:15:22:55
Block: 1132321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303173 RingCT/type: yes/0
Extra: 01d5f74eb2a22f91c1416a1363661a5cfe2611d0c214492c857fe51b502e120e78021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b110b1e970da73b9f69e23b05c5443853bb8114dc223e7d211ae0f39cf5fab56 0.600000000000 1615234 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": 1132331, "vin": [ { "gen": { "height": 1132321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b110b1e970da73b9f69e23b05c5443853bb8114dc223e7d211ae0f39cf5fab56" } } ], "extra": [ 1, 213, 247, 78, 178, 162, 47, 145, 193, 65, 106, 19, 99, 102, 26, 92, 254, 38, 17, 208, 194, 20, 73, 44, 133, 127, 229, 27, 80, 46, 18, 14, 120, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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