Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c077d7e9a5b4c1393426e19b0a9b8009cd57c8f1fce52a262cb7315513d7f31

Tx prefix hash: 52c1963cca014419cf48f9a6b37dea764791555220cf56fb8c7e724ebd877503
Tx public key: 05e685822ae94168fb17f2b9b5f8cf58ae3472e20dc8d1a303c6402f8a217f28
Timestamp: 1725928390 Timestamp [UCT]: 2024-09-10 00:33:10 Age [y:d:h:m:s]: 00:121:03:51:10
Block: 1106705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86645 RingCT/type: yes/0
Extra: 0105e685822ae94168fb17f2b9b5f8cf58ae3472e20dc8d1a303c6402f8a217f2802110000001ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b7946b96c94e18e81d45cf491afd6034100adb08679e3b1a7dee7a93dfa2a5b 0.600000000000 1584306 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": 1106715, "vin": [ { "gen": { "height": 1106705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b7946b96c94e18e81d45cf491afd6034100adb08679e3b1a7dee7a93dfa2a5b" } } ], "extra": [ 1, 5, 230, 133, 130, 42, 233, 65, 104, 251, 23, 242, 185, 181, 248, 207, 88, 174, 52, 114, 226, 13, 200, 209, 163, 3, 198, 64, 47, 138, 33, 127, 40, 2, 17, 0, 0, 0, 28, 233, 20, 221, 21, 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