Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f2ab3eb6c1164109a97461a395b13da3bc8f12079f90bb4c78f9f3b62e21c3c

Tx prefix hash: c6c3afdf74ae88153e2bc331a4115560e3a2354bb44a361eeaa3f017adfbdd31
Tx public key: 0dfa6a46bce1d60a023e2950e4f1923124b8105586d1bf7ee2a81bf58a9794ea
Timestamp: 1583747487 Timestamp [UCT]: 2020-03-09 09:51:27 Age [y:d:h:m:s]: 05:064:03:50:01
Block: 78930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201700 RingCT/type: yes/0
Extra: 010dfa6a46bce1d60a023e2950e4f1923124b8105586d1bf7ee2a81bf58a9794ea0211000000054ac5aa02000000000000000000

1 output(s) for total of 336.103423470000 dcy

stealth address amount amount idx
00: 01806e0901a53312ac961a551db315274f3c1e438a13eb8f9e4e6945eb497b6e 336.103423470000 144614 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": 78940, "vin": [ { "gen": { "height": 78930 } } ], "vout": [ { "amount": 336103423470, "target": { "key": "01806e0901a53312ac961a551db315274f3c1e438a13eb8f9e4e6945eb497b6e" } } ], "extra": [ 1, 13, 250, 106, 70, 188, 225, 214, 10, 2, 62, 41, 80, 228, 241, 146, 49, 36, 184, 16, 85, 134, 209, 191, 126, 226, 168, 27, 245, 138, 151, 148, 234, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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