Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56318e7980a9dbcf64bb51733a38071128e1b20e6b2a175956fd7686e9a57427

Tx prefix hash: cdc2ec98aae390257f8c272d8641d54e32625c12c9f577e1e98928fb658bcd36
Tx public key: 4c81a30ee9bde747b7024d1910d48e48d250efe8662040ce335f0ee005841d04
Timestamp: 1725292082 Timestamp [UCT]: 2024-09-02 15:48:02 Age [y:d:h:m:s]: 00:271:05:28:34
Block: 1101432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193738 RingCT/type: yes/0
Extra: 014c81a30ee9bde747b7024d1910d48e48d250efe8662040ce335f0ee005841d04021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d5261037db3b958c674e6de9778f7ef790f1e346aa8f992aad27a18a3db6b9 0.600000000000 1577477 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": 1101442, "vin": [ { "gen": { "height": 1101432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d5261037db3b958c674e6de9778f7ef790f1e346aa8f992aad27a18a3db6b9" } } ], "extra": [ 1, 76, 129, 163, 14, 233, 189, 231, 71, 183, 2, 77, 25, 16, 212, 142, 72, 210, 80, 239, 232, 102, 32, 64, 206, 51, 95, 14, 224, 5, 132, 29, 4, 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