Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ee3445971a77b20f81233ac9fff145b6fcc03d25c9f5bb2ea842aba9cc56d7

Tx prefix hash: 97d48dde4bf9b8c0ae51b7b71db9418962451bde8124712e828f54bbcc413f51
Tx public key: ae4ae001ff5950c1397a61c7fb05f1f4e89b50c594432d7ad75010e7807b8c3d
Timestamp: 1582286920 Timestamp [UCT]: 2020-02-21 12:08:40 Age [y:d:h:m:s]: 05:021:19:23:41
Block: 69429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168829 RingCT/type: yes/0
Extra: 01ae4ae001ff5950c1397a61c7fb05f1f4e89b50c594432d7ad75010e7807b8c3d021100000001724f989b000000000000000000

1 output(s) for total of 361.371340032000 dcy

stealth address amount amount idx
00: 46619deefce007e21726039ad279f42c41e725469d2654278f713741188ccc31 361.371340032000 128063 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": 69439, "vin": [ { "gen": { "height": 69429 } } ], "vout": [ { "amount": 361371340032, "target": { "key": "46619deefce007e21726039ad279f42c41e725469d2654278f713741188ccc31" } } ], "extra": [ 1, 174, 74, 224, 1, 255, 89, 80, 193, 57, 122, 97, 199, 251, 5, 241, 244, 232, 155, 80, 197, 148, 67, 45, 122, 215, 80, 16, 231, 128, 123, 140, 61, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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