Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbacf42754ef13b3cfde15a3bafd71fef8434252b73ea6175c065542b12ea293

Tx prefix hash: 468e7a0c6d6937f0f64a71164c25db71617f1b0f91a05447830341fd09d6783b
Tx public key: 9ccd0dd3c2334e711fc45698b37900787ee46f98f6e33514d76e33287ac403f8
Timestamp: 1583537692 Timestamp [UCT]: 2020-03-06 23:34:52 Age [y:d:h:m:s]: 05:101:23:11:41
Block: 77829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228004 RingCT/type: yes/0
Extra: 019ccd0dd3c2334e711fc45698b37900787ee46f98f6e33514d76e33287ac403f802110000001981a90efe000000000000000000

1 output(s) for total of 338.938581676000 dcy

stealth address amount amount idx
00: e25ff909e970033d8721fefa7b72c2039635887e4ee3e0e13ee5ce1c9340f5b9 338.938581676000 143040 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": 77839, "vin": [ { "gen": { "height": 77829 } } ], "vout": [ { "amount": 338938581676, "target": { "key": "e25ff909e970033d8721fefa7b72c2039635887e4ee3e0e13ee5ce1c9340f5b9" } } ], "extra": [ 1, 156, 205, 13, 211, 194, 51, 78, 113, 31, 196, 86, 152, 179, 121, 0, 120, 126, 228, 111, 152, 246, 227, 53, 20, 215, 110, 51, 40, 122, 196, 3, 248, 2, 17, 0, 0, 0, 25, 129, 169, 14, 254, 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