Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26dfbe6fd5bc31c16e97a40fafbc55953858b75115a30ba399b502433721af7c

Tx prefix hash: e8182ecf8fd089261f4a3be1b1c79319ff1d48fa61aa05774452aa3840bc89d3
Tx public key: 75c6a1ea45e60fdc47c1ecb04644d54f5205838b7d70614d400ad1f123d57f1f
Timestamp: 1719672661 Timestamp [UCT]: 2024-06-29 14:51:01 Age [y:d:h:m:s]: 00:259:17:58:37
Block: 1054832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185615 RingCT/type: yes/0
Extra: 0175c6a1ea45e60fdc47c1ecb04644d54f5205838b7d70614d400ad1f123d57f1f0211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536fa2002cf45f9d23dd7a92fc80c284e623d558d02f54474832ec4bbf802dc8 0.600000000000 1525223 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": 1054842, "vin": [ { "gen": { "height": 1054832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536fa2002cf45f9d23dd7a92fc80c284e623d558d02f54474832ec4bbf802dc8" } } ], "extra": [ 1, 117, 198, 161, 234, 69, 230, 15, 220, 71, 193, 236, 176, 70, 68, 213, 79, 82, 5, 131, 139, 125, 112, 97, 77, 64, 10, 209, 241, 35, 213, 127, 31, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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