Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57bfcd871bd4b5d98fc445ccba277b5347ff93bc7096c3810f5a016fb9331cb7

Tx prefix hash: bd2e284e9490c5e018ba138003046c2ff2225fdfb7ccc5f918957a776fe12b83
Tx public key: c47a82781850f4a1cdf1b6864f4349fceeafec533a22c09291ef6f0fb0ff7875
Timestamp: 1582002501 Timestamp [UCT]: 2020-02-18 05:08:21 Age [y:d:h:m:s]: 05:062:03:16:35
Block: 67251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197484 RingCT/type: yes/0
Extra: 01c47a82781850f4a1cdf1b6864f4349fceeafec533a22c09291ef6f0fb0ff787502110000000e4943cd9f000000000000000000

1 output(s) for total of 367.426374493000 dcy

stealth address amount amount idx
00: 3f9d5cdfa36dc8e03fd282778c19d11f19b631c24b5a8391ba5a7d1825932039 367.426374493000 123912 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": 67261, "vin": [ { "gen": { "height": 67251 } } ], "vout": [ { "amount": 367426374493, "target": { "key": "3f9d5cdfa36dc8e03fd282778c19d11f19b631c24b5a8391ba5a7d1825932039" } } ], "extra": [ 1, 196, 122, 130, 120, 24, 80, 244, 161, 205, 241, 182, 134, 79, 67, 73, 252, 238, 175, 236, 83, 58, 34, 192, 146, 145, 239, 111, 15, 176, 255, 120, 117, 2, 17, 0, 0, 0, 14, 73, 67, 205, 159, 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