Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04dc4aca7dd8d6a3fa89d73817a291b7d945b59cf820f86a57299275562bd54f

Tx prefix hash: b68e29a5afa99a0941310c6324b6c2704bdd14c6c4c34b405ad963f41e5f2eb3
Tx public key: 008ba328e96cecf1286a109f0f124129a6365532d74d7708f39e05c271cec072
Timestamp: 1694434350 Timestamp [UCT]: 2023-09-11 12:12:30 Age [y:d:h:m:s]: 01:202:10:57:40
Block: 845786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405791 RingCT/type: yes/0
Extra: 01008ba328e96cecf1286a109f0f124129a6365532d74d7708f39e05c271cec07202110000000233af99f4000000000000000000

1 output(s) for total of 0.967297226000 dcy

stealth address amount amount idx
00: 1a483cee8d6fd733a4b163289d68f69ddfbde37c234fe1b106df23f0eee9c88a 0.967297226000 1299204 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": 845796, "vin": [ { "gen": { "height": 845786 } } ], "vout": [ { "amount": 967297226, "target": { "key": "1a483cee8d6fd733a4b163289d68f69ddfbde37c234fe1b106df23f0eee9c88a" } } ], "extra": [ 1, 0, 139, 163, 40, 233, 108, 236, 241, 40, 106, 16, 159, 15, 18, 65, 41, 166, 54, 85, 50, 215, 77, 119, 8, 243, 158, 5, 194, 113, 206, 192, 114, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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