Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec1f52e57563b11b24b485cd4db9491ed8cf0971c5d4f0c8299b472835351030

Tx prefix hash: 376c7c05d8b862d014b8307a93f469e52991f692416e32260f1e53917b61bff8
Tx public key: e72063cc25a5d3a36d0a78cf95a59a9f1c37164039fc4d80d566c8709cdda538
Timestamp: 1637822358 Timestamp [UCT]: 2021-11-25 06:39:18 Age [y:d:h:m:s]: 03:075:13:21:38
Block: 381645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 832658 RingCT/type: yes/0
Extra: 01e72063cc25a5d3a36d0a78cf95a59a9f1c37164039fc4d80d566c8709cdda538021100000002e9564d6f000000000000000000

1 output(s) for total of 33.390086301000 dcy

stealth address amount amount idx
00: 8cc731d6c833a4651703c8c8daf206fe04e98e4ab3f0b425a78775743742b8ea 33.390086301000 770955 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": 381655, "vin": [ { "gen": { "height": 381645 } } ], "vout": [ { "amount": 33390086301, "target": { "key": "8cc731d6c833a4651703c8c8daf206fe04e98e4ab3f0b425a78775743742b8ea" } } ], "extra": [ 1, 231, 32, 99, 204, 37, 165, 211, 163, 109, 10, 120, 207, 149, 165, 154, 159, 28, 55, 22, 64, 57, 252, 77, 128, 213, 102, 200, 112, 156, 221, 165, 56, 2, 17, 0, 0, 0, 2, 233, 86, 77, 111, 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