Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46ca1a10b309ded1c4aabd8fcfd8c97dd130db2df82917491b20cb5b7c672ed4

Tx prefix hash: 31239c7743c300b650fd5e16ae3cbb0d95b8d4ad6dc576e6b6e693d5ab8c5334
Tx public key: dda78a27dcad1ada4b5204e37bbecbcdb90036f3a88b6667eb85cd4bcd3546e8
Timestamp: 1695493554 Timestamp [UCT]: 2023-09-23 18:25:54 Age [y:d:h:m:s]: 01:196:19:32:17
Block: 854578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401729 RingCT/type: yes/0
Extra: 01dda78a27dcad1ada4b5204e37bbecbcdb90036f3a88b6667eb85cd4bcd3546e80211000000044b8f5122000000000000000000

1 output(s) for total of 0.904541264000 dcy

stealth address amount amount idx
00: 4184e7e32c9457e0507646a39467f3ebc7be7beffe661d60cf201adeddc5d0c2 0.904541264000 1308560 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": 854588, "vin": [ { "gen": { "height": 854578 } } ], "vout": [ { "amount": 904541264, "target": { "key": "4184e7e32c9457e0507646a39467f3ebc7be7beffe661d60cf201adeddc5d0c2" } } ], "extra": [ 1, 221, 167, 138, 39, 220, 173, 26, 218, 75, 82, 4, 227, 123, 190, 203, 205, 185, 0, 54, 243, 168, 139, 102, 103, 235, 133, 205, 75, 205, 53, 70, 232, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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