Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2117a4f3e32ae05b1d5b380b598b2ec26a7dbfc24d342ab1bfdc2626eb2a482a

Tx prefix hash: 0d895949274398b9ea7169f9803f70e67ae3187624e05e8d201585aecaa35289
Tx public key: 85e0171ebe1ce315627ccd4a75d7dd2fc4391c93eee2ea48f7fce202fb1c77ce
Timestamp: 1719101296 Timestamp [UCT]: 2024-06-23 00:08:16 Age [y:d:h:m:s]: 01:139:19:32:37
Block: 1050086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358497 RingCT/type: yes/0
Extra: 0185e0171ebe1ce315627ccd4a75d7dd2fc4391c93eee2ea48f7fce202fb1c77ce021100000001c5f9cfd0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e4cee735af8177a93ae3a121c7caf5e73b4c26a57247fffe46281c8dae0ac54 0.600000000000 1520241 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": 1050096, "vin": [ { "gen": { "height": 1050086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e4cee735af8177a93ae3a121c7caf5e73b4c26a57247fffe46281c8dae0ac54" } } ], "extra": [ 1, 133, 224, 23, 30, 190, 28, 227, 21, 98, 124, 205, 74, 117, 215, 221, 47, 196, 57, 28, 147, 238, 226, 234, 72, 247, 252, 226, 2, 251, 28, 119, 206, 2, 17, 0, 0, 0, 1, 197, 249, 207, 208, 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