Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f400a39c93e34a5553d5f587896fbaa94ffeccdbf8a93181b0e311c28a362f2e

Tx prefix hash: 929b1132bebfd330ae77d9c4333bba821a1915b88f7f181e5faa60c16ada069d
Tx public key: e8a9f49a9040764fd194928ad6eb009f1882fa722bde2924040ee846c8f830b2
Timestamp: 1643502875 Timestamp [UCT]: 2022-01-30 00:34:35 Age [y:d:h:m:s]: 03:024:04:50:52
Block: 428127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 796441 RingCT/type: yes/0
Extra: 01e8a9f49a9040764fd194928ad6eb009f1882fa722bde2924040ee846c8f830b20211000000012e6b1fd5000000000000000000

1 output(s) for total of 23.411963364000 dcy

stealth address amount amount idx
00: 00a5eee6c0ac04f8f20d467c2cb3bca0db1d527d812524b7cacd59356d453ce9 23.411963364000 837445 of 0

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": 428137, "vin": [ { "gen": { "height": 428127 } } ], "vout": [ { "amount": 23411963364, "target": { "key": "00a5eee6c0ac04f8f20d467c2cb3bca0db1d527d812524b7cacd59356d453ce9" } } ], "extra": [ 1, 232, 169, 244, 154, 144, 64, 118, 79, 209, 148, 146, 138, 214, 235, 0, 159, 24, 130, 250, 114, 43, 222, 41, 36, 4, 14, 232, 70, 200, 248, 48, 178, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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