Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d146f8c8fd004c3ed15e3e8fd451cbfa9bcca4fd8fb63e2f9e174fd9f276b7

Tx prefix hash: d5955e488c42b2c32ac2c1f393e90f6930fa1e1820062ed3f52b101e619a8de3
Tx public key: 1d68564464bd912864ff6bb78e619742c2603e1c6f8ed1a12eee0ffbd9f0c89d
Timestamp: 1710768198 Timestamp [UCT]: 2024-03-18 13:23:18 Age [y:d:h:m:s]: 00:336:09:44:07
Block: 981034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240476 RingCT/type: yes/0
Extra: 011d68564464bd912864ff6bb78e619742c2603e1c6f8ed1a12eee0ffbd9f0c89d021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3d7c1dcf0b55c8c193d18235c1941b0ec64f1497d5432ac2760812dd79f29e8 0.600000000000 1441119 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": 981044, "vin": [ { "gen": { "height": 981034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3d7c1dcf0b55c8c193d18235c1941b0ec64f1497d5432ac2760812dd79f29e8" } } ], "extra": [ 1, 29, 104, 86, 68, 100, 189, 145, 40, 100, 255, 107, 183, 142, 97, 151, 66, 194, 96, 62, 28, 111, 142, 209, 161, 46, 238, 15, 251, 217, 240, 200, 157, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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