Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495ec3d627791b20ba52856d78349496bc5ecd2c78eddbc068cad187dd9aeec8

Tx prefix hash: e930de20f589ea68e5069325be3d13b8146a692788473203ad9a18f9ccff464d
Tx public key: 9b948cdafe8ea69c76c770414cf427bd2875ed7342b83f1cc4aac63ee7e19ba6
Timestamp: 1702250390 Timestamp [UCT]: 2023-12-10 23:19:50 Age [y:d:h:m:s]: 01:334:20:54:17
Block: 910401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498201 RingCT/type: yes/0
Extra: 019b948cdafe8ea69c76c770414cf427bd2875ed7342b83f1cc4aac63ee7e19ba6021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5abf3fcc543c7dcfeb38ad5a64cb5f64f638acf4b9bb7ee1c482d6f498c872d0 0.600000000000 1367556 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": 910411, "vin": [ { "gen": { "height": 910401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5abf3fcc543c7dcfeb38ad5a64cb5f64f638acf4b9bb7ee1c482d6f498c872d0" } } ], "extra": [ 1, 155, 148, 140, 218, 254, 142, 166, 156, 118, 199, 112, 65, 76, 244, 39, 189, 40, 117, 237, 115, 66, 184, 63, 28, 196, 170, 198, 62, 231, 225, 155, 166, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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