Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd09f7d28c6c630a5db3fb2ad0cd3939f79d6cb5c48653773dc9144352865bfd

Tx prefix hash: 7d84b76da517281a7646bc0818057bdc6902f1e6636755fda568a126895ad624
Tx public key: 842c0c55ac3142ad76f72879ce2eb6c02c28c25958f960fc48933a7b773acae6
Timestamp: 1582972406 Timestamp [UCT]: 2020-02-29 10:33:26 Age [y:d:h:m:s]: 05:074:01:36:12
Block: 73934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207364 RingCT/type: yes/0
Extra: 01842c0c55ac3142ad76f72879ce2eb6c02c28c25958f960fc48933a7b773acae6021100000224724f989b000000000000000000

1 output(s) for total of 349.167853500000 dcy

stealth address amount amount idx
00: 5e6e536d607ad4d383c96ea4d8a303c28b25b262d47b2e29a0ed41d46640c63c 349.167853500000 136631 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": 73944, "vin": [ { "gen": { "height": 73934 } } ], "vout": [ { "amount": 349167853500, "target": { "key": "5e6e536d607ad4d383c96ea4d8a303c28b25b262d47b2e29a0ed41d46640c63c" } } ], "extra": [ 1, 132, 44, 12, 85, 172, 49, 66, 173, 118, 247, 40, 121, 206, 46, 182, 192, 44, 40, 194, 89, 88, 249, 96, 252, 72, 147, 58, 123, 119, 58, 202, 230, 2, 17, 0, 0, 2, 36, 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