Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae132b9d1b41ed5b8af46934666abf1b5071085bc93f7335411227f76c5bc79b

Tx prefix hash: 6d403f98000775e61949d539d340f0d359e175c917aab2089cd710a546ebd8b5
Tx public key: e9e1c8ec97a0bae5d2653f19279015cc4c6dd77b3076e6b6bde4bb12944274e8
Timestamp: 1719383784 Timestamp [UCT]: 2024-06-26 06:36:24 Age [y:d:h:m:s]: 00:274:19:00:26
Block: 1052442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196350 RingCT/type: yes/0
Extra: 01e9e1c8ec97a0bae5d2653f19279015cc4c6dd77b3076e6b6bde4bb12944274e80211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 422d9ac70d1e1c18ab40c29db07cad7ce2cef4fea4f0b75bae870feea4c6c2ad 0.600000000000 1522769 of 15

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": 1052452, "vin": [ { "gen": { "height": 1052442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "422d9ac70d1e1c18ab40c29db07cad7ce2cef4fea4f0b75bae870feea4c6c2ad" } } ], "extra": [ 1, 233, 225, 200, 236, 151, 160, 186, 229, 210, 101, 63, 25, 39, 144, 21, 204, 76, 109, 215, 123, 48, 118, 230, 182, 189, 228, 187, 18, 148, 66, 116, 232, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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