Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77bb07361050509b2d212990252fd399c2281542ec0479645dadb2504dda6a8e

Tx prefix hash: 9edca1331d5112349767b041cdf9f428f045cb268901dd9cff0ebf94264b85cc
Tx public key: be3571fd7bbc5e284e70d1a23c5f77e0713102db4e4ed08ebca0e97b1f0d17e3
Timestamp: 1710785947 Timestamp [UCT]: 2024-03-18 18:19:07 Age [y:d:h:m:s]: 00:315:01:02:23
Block: 981191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225240 RingCT/type: yes/0
Extra: 01be3571fd7bbc5e284e70d1a23c5f77e0713102db4e4ed08ebca0e97b1f0d17e302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a76b77a1326bd8294d54d48616d7aec07c1f5e209ad38a9bbd673c22fe1aa708 0.600000000000 1441284 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": 981201, "vin": [ { "gen": { "height": 981191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a76b77a1326bd8294d54d48616d7aec07c1f5e209ad38a9bbd673c22fe1aa708" } } ], "extra": [ 1, 190, 53, 113, 253, 123, 188, 94, 40, 78, 112, 209, 162, 60, 95, 119, 224, 113, 49, 2, 219, 78, 78, 208, 142, 188, 160, 233, 123, 31, 13, 23, 227, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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