Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c35464e4fc319f9c9f6bf9fe58ec59acc565693fcce935421ed36d2664aecf5

Tx prefix hash: 0d537636232b008e79d9c625563cec6bf3716dd8700f621618db70a82c385e15
Tx public key: d0a3b72be03f0ffac22dc11e5bc1419412ffc9a7b75fbaf01e600fc9eda517c5
Timestamp: 1731501409 Timestamp [UCT]: 2024-11-13 12:36:49 Age [y:d:h:m:s]: 00:010:18:39:54
Block: 1152817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7714 RingCT/type: yes/0
Extra: 01d0a3b72be03f0ffac22dc11e5bc1419412ffc9a7b75fbaf01e600fc9eda517c50211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cfa3f0efdfca7b10d4ae47f2df9fa0c2c89541eddd0e08fae11943423454bd5 0.600000000000 1638422 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": 1152827, "vin": [ { "gen": { "height": 1152817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cfa3f0efdfca7b10d4ae47f2df9fa0c2c89541eddd0e08fae11943423454bd5" } } ], "extra": [ 1, 208, 163, 183, 43, 224, 63, 15, 250, 194, 45, 193, 30, 91, 193, 65, 148, 18, 255, 201, 167, 183, 95, 186, 240, 30, 96, 15, 201, 237, 165, 23, 197, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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